personSingle person by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Person unique identifier | |
| age | No | Character age | |
| url | No | API URL for this person | |
| name | No | Character/person name | |
| films | No | Array of film IDs | |
| gender | No | Character gender | |
| species | No | Species ID | |
| eye_color | No | Eye color | |
| hair_color | No | Hair color |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "id": "ba510c6d-61ae-45a6-8b5a-3dd06b4bed34"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "age": {
+ "description": "Character age",
+ "type": "string"
+ },
+ "eye_color": {
+ "description": "Eye color",
+ "type": "string"
+ },
+ "films": {
+ "description": "Array of film IDs",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "gender": {
+ "description": "Character gender",
+ "type": "string"
+ },
+ "hair_color": {
+ "description": "Hair color",
+ "type": "string"
+ },
+ "id": {
+ "description": "Person unique identifier",
+ "type": "string"
+ },
+ "name": {
+ "description": "Character/person name",
+ "type": "string"
+ },
+ "species": {
+ "description": "Species ID",
+ "type": "string"
+ },
+ "url": {
+ "description": "API URL for this person",
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the 'single' cardinality and id-based lookup, but does not disclose behavior for missing ids or any open-world nuances; with strong annotations this is acceptable but minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single five-word sentence, immediately front-loaded with the tool's core function. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (one required parameter), rich annotations, and presence of an output schema, the brief description covers the essential invocation detail. However, it could be more helpful by naming sibling tools or noting when to use this vs people/entity_profile, so it is not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has no description for the 'id' parameter (0% coverage), and the description only says 'by id', adding minimal semantic value. The parameter name and example UUID in the schema already convey most of the meaning, so the description does not substantially compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource (person) and the access pattern (by id), clearly distinguishing it from sibling list tools like 'people'. It lacks an explicit verb, but 'single person by id' unambiguously implies retrieval of one record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to choose this tool over siblings such as people, entity_profile, or compare_entities. The description only implies that it is for direct id lookups, with no exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.