get_great_people
Retrieve lists of claimed and available great people for recruitment planning.
Instructions
Get Great People that have been claimed and those available for recruitment.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve lists of claimed and available great people for recruitment planning.
Get Great People that have been claimed and those available for recruitment.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; the description does not disclose behavior beyond the basic action. Missing info on side effects, permissions, or return format. For a tool with no annotations, the description should provide more context.
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?
Extremely concise single sentence that clearly states purpose. 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?
Minimal but adequate for a simple retrieval tool with no parameters. However, lacks information on what the response contains (e.g., list of great people with statuses). With no output schema, description should provide more context.
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?
No parameters exist, schema coverage is 100%. The description adds no parameter info, but none is needed. Baseline for 0 parameters is 4.
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 clearly identifies the resource ('Great People') and the action ('Get') and distinguishes between claimed and available. However, it does not differentiate from the sibling tool 'get_great_people_culture'.
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 on when to use this tool versus siblings like 'get_great_people_culture'. Lacks context on prerequisites or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lowrykun/civ6mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server