Skip to main content
Glama

Search People

search_people
Read-onlyIdempotent

Search Star Wars characters by name. Returns name, physical attributes, birth year, gender, and homeworld URL.

Input Schema

NameRequiredDescriptionDefault
queryYesCharacter name to search for (e.g., "Luke")

Output Schema

NameRequiredDescriptionDefault
countYesTotal count of matching characters
resultsYesList of matching characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "Luke"
      +  },
      +  {
      +    "query": "Darth Vader"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Total count of matching characters",
      +      "type": "number"
      +    },
      +    "results": {
      +      "description": "List of matching characters",
      +      "items": {
      +        "properties": {
      +          "birth_year": {
      +            "description": "Birth year",
      +            "type": "string"
      +          },
      +          "eye_color": {
      +            "description": "Eye color",
      +            "type": "string"
      +          },
      +          "gender": {
      +            "description": "Gender",
      +            "type": "string"
      +          },
      +          "hair_color": {
      +            "description": "Hair color",
      +            "type": "string"
      +          },
      +          "height": {
      +            "description": "Height",
      +            "type": "string"
      +          },
      +          "homeworld": {
      +            "description": "Homeworld URL",
      +            "type": "string"
      +          },
      +          "mass": {
      +            "description": "Mass",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Character name",
      +            "type": "string"
      +          },
      +          "skin_color": {
      +            "description": "Skin color",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Character URL",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "height",
      +          "mass",
      +          "hair_color",
      +          "skin_color",
      +          "eye_color",
      +          "birth_year",
      +          "gender",
      +          "homeworld",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "query": "Luke"
      -  },
      -  {
      -    "query": "Darth Vader"
      -  }
      -]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "count": {
      -      "description": "Total count of matching characters",
      -      "type": "number"
      -    },
      -    "results": {
      -      "description": "List of matching characters",
      -      "items": {
      -        "properties": {
      -          "birth_year": {
      -            "description": "Birth year",
      -            "type": "string"
      -          },
      -          "eye_color": {
      -            "description": "Eye color",
      -            "type": "string"
      -          },
      -          "gender": {
      -            "description": "Gender",
      -            "type": "string"
      -          },
      -          "hair_color": {
      -            "description": "Hair color",
      -            "type": "string"
      -          },
      -          "height": {
      -            "description": "Height",
      -            "type": "string"
      -          },
      -          "homeworld": {
      -            "description": "Homeworld URL",
      -            "type": "string"
      -          },
      -          "mass": {
      -            "description": "Mass",
      -            "type": "string"
      -          },
      -          "name": {
      -            "description": "Character name",
      -            "type": "string"
      -          },
      -          "skin_color": {
      -            "description": "Skin color",
      -            "type": "string"
      -          },
      -          "url": {
      -            "description": "Character URL",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "name",
      -          "height",
      -          "mass",
      -          "hair_color",
      -          "skin_color",
      -          "eye_color",
      -          "birth_year",
      -          "gender",
      -          "homeworld",
      -          "url"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "count",
      -    "results"
      -  ],
      -  "type": "object"
      -}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "description": "Total count of matching characters",
      +      "type": "number"
      +    },
      +    "results": {
      +      "description": "List of matching characters",
      +      "items": {
      +        "properties": {
      +          "birth_year": {
      +            "description": "Birth year",
      +            "type": "string"
      +          },
      +          "eye_color": {
      +            "description": "Eye color",
      +            "type": "string"
      +          },
      +          "gender": {
      +            "description": "Gender",
      +            "type": "string"
      +          },
      +          "hair_color": {
      +            "description": "Hair color",
      +            "type": "string"
      +          },
      +          "height": {
      +            "description": "Height",
      +            "type": "string"
      +          },
      +          "homeworld": {
      +            "description": "Homeworld URL",
      +            "type": "string"
      +          },
      +          "mass": {
      +            "description": "Mass",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Character name",
      +            "type": "string"
      +          },
      +          "skin_color": {
      +            "description": "Skin color",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Character URL",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "height",
      +          "mass",
      +          "hair_color",
      +          "skin_color",
      +          "eye_color",
      +          "birth_year",
      +          "gender",
      +          "homeworld",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "Luke"
      +  },
      +  {
      +    "query": "Darth Vader"
      +  }
      +]
  5. First observed

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already disclose read-only, non-destructive, open-world, and idempotent behavior. The description adds return fields, but this information is also available in the output schema. It does not disclose additional behavioral traits such as pagination, result limits, or matching rules.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It states the action, resource, and result fields efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter search tool with rich annotations and an output schema, the description is adequate. It covers the core search action and return information without requiring additional detail. Minor gaps like pagination or matching behavior could be addressed but are not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with a clear description and examples for the query parameter. The description's phrase 'by name' simply restates the schema, adding no new semantic detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches Star Wars characters by name and lists what it returns. It is distinct from sibling tools like search_within because it specifically targets people characters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternative guidance is provided. Usage is implied by the tool's purpose: use it when you need to find character data by name. There are no exclusions or mention of siblings that might be more appropriate for other cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.