[Feat]: Add tags field to AgentCard for agent categorization
- Lingua principale
- Shell
- Stelle
- 25.7k
- Fork
- 2.6k
- Merge medio
- 3g 6h
- PR unite (30g)
- 16
Descrizione
### Is your feature request related to a problem? Please describe.
_No response_
### Describe the solution you'd like
Add an optional `agent_type` field (string) to the `AgentCard` message that allows agents to declare their type/category.
Example values: "llm", "workflow", "assistant", "retrieval", "code-executor", or any custom value.
Benefits:
- Helps consumers quickly identify the kind of agent they are interacting with
- Enables filtering and sorting in agent registries and catalogs
- Flexible string type (not enum) allows any custom categorization without protocol changes
- Optional field ensures backward compatibility
Changes required:
- Add `optional string agent_type = 20;` to AgentCard in `a2a.proto`
- Update specification documentation
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Find the a2a.proto file, locate the AgentCard message definition, and add the optional string field with the correct field number. Update any related specification documentation. Verify the change by checking that the protocol buffer compiles correctly.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Ambito
- backend-api-design
- Tipo di issue
- Funzionalità
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Stato di attività
- Ferma
- Chiarezza
- Specificata chiaramente
- Idoneità per principianti
- 65/100