Skip to main content
Glama

Little Works

who_can_do

Alias of source_people — who has the skills to do something in a place.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "need": "<need>"
    },
    "name": "who_can_do"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes
placeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing: not whether the call is read-only, what it returns, whether it paginates, or what permissions are needed. Saying it is an alias of source_people implies it shares that tool's behavior, which is the only behavioral signal present.

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?

A single short sentence with zero padding, and the sibling relationship is front-loaded. Nothing is wasted or buried.

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

Completeness2/5

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

With no annotations, no output schema, and both parameters undocumented in the schema, this one-sentence description leaves too much unknown for a tool the agent must choose between and call correctly. It would need at minimum a clear statement of what is returned and why an agent would pick it over source_people.

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 description coverage is 0%, so the description must compensate, and it does partially: 'skills to do something' points at the required 'need' parameter and 'in a place' points at the optional 'place' parameter. It still gives no format, example, or constraint for either value, so 'need' remains ambiguous (a skill name? a free-text task?).

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

Purpose3/5

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

The phrase 'who has the skills to do something in a place' hints at a people/skill lookup, but there is no specific verb and the leading claim 'Alias of source_people' actually obscures the purpose by framing the tool as a duplicate. The reference to source_people does give the agent a sibling anchor, which raises it above pure vagueness, but the agent still cannot tell what this tool does that source_people does not.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool rather than source_people, and no condition or exclusion is given. Calling it an 'alias' arguably creates a usage question (which of the two should be called?) rather than answering one, so the agent is left to infer routing entirely on its own.

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.

Resources