Skip to main content
Glama

APP NAVI

search_developers

開発者を検索する。contract_work は開発者本人の申告(yes/no/undecided、null は未確認)。Search developers; contractWork is self-declared.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_developers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo開発者名のキーワード / name keyword
contract_onlyNo受託開発を受けると申告している開発者だけ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add genuinely useful behavioral context: contract_work is self-declared (yes/no/undecided, null = unverified), which tells the agent to treat that field as unverified data. However, it says nothing about result ordering, pagination behavior, or what a search response contains.

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

Conciseness4/5

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

Two short sentences, purpose front-loaded, with the caveat about self-declared data immediately following. The Japanese/English duplication is slightly redundant but justified for bilingual clarity and costs little.

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?

With no annotations and no output schema, the description does reasonable work by defining the semantics of a returned attribute and the meaning of declared values. Gaps remain around how contract_only interacts with contract_work and how many results/pagination behave, which keeps it from a 5.

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 67%; query and contract_only are documented in the schema, while limit is not. The description adds meaning about a contract_work attribute (its yes/no/undecided/null semantics) that appears nowhere in the schema, which is valuable, but it never explains how that relates to the documented boolean parameter contract_only, leaving a naming gap the agent must guess at.

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

Purpose4/5

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

The description opens with a specific verb+resource ('開発者を検索する' / 'Search developers'), which matches the tool name and clearly signals a search operation rather than a single-record fetch. It does not explicitly contrast itself with siblings such as get_developer or get_ranking, so it stops short of full differentiation.

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 versus get_developer (single lookup) or get_ranking, and no exclusions or prerequisites. Usage is only implied by the word 'search'.

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