Skip to main content
Glama

APP NAVI

get_developer

slug で 1 人(1 チーム)の開発者と、掲載しているアプリ一覧を取得する。

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": {
      "slug": "<slug>"
    },
    "name": "get_developer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 valuable behavioral context by stating the response includes both the developer record and their published apps, but it says nothing about not-found handling, permissions, or whether unpublished apps are included.

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 front-loaded sentence with no filler; the resource, the key, and the returned payload all appear in the first clause sequence.

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?

There is no output schema, and the description compensates by stating what is returned (developer plus app list). For a one-parameter read tool this is nearly complete, with only slug format and failure behavior left unaddressed.

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 0%, so the description must explain the single parameter. It does convey that slug identifies exactly one developer (or team), which is meaning the bare {"slug": string} schema does not provide, but it gives no format hint or example of a valid slug.

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 names a specific verb (取得する, retrieve) and resource (開発者, developer), scoped by slug, and also discloses the secondary payload (掲載しているアプリ一覧, the list of published apps). It is clearly distinguishable from get_app and get_ranking; it only weakly signals that it is the exact-lookup counterpart to search_developers.

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?

The phrase "slug で 1 人" implies exact-key lookup rather than search, which nudges an agent toward this tool over search_developers when a slug is known. However, there is no explicit when-to-use/when-not-to-use statement, no mention of the alternative by name, and no guidance on what to do when the slug is unknown or does not exist.

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