Skip to main content
Glama

Artbook Society — Public Catalog

Get publisher profile

get_editor
Read-onlyIdempotent

Fetch full public details for a single editor by their numeric id.

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": {
      "id": "<id>"
    },
    "name": "get_editor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric editor id.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
logoNo
titleNo
websiteNo
biographyNo

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one piece of context—that only 'public' details are returned—but says nothing about error behavior for an unknown id, which is the main thing an agent could get wrong.

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?

One front-loaded sentence with no filler. It is efficient, though it is on the thin side for a tool with this much annotation context to build on.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Still, the description leaves an agent without the id-provenance hint or any sibling routing, which is the remaining gap for an otherwise simple one-param lookup.

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% and the single id parameter is already documented as 'Numeric editor id.' The description repeats 'numeric id' without adding format, range, or sourcing guidance, so baseline 3 applies.

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?

States a specific verb and resource: fetch full public details for a single editor. The 'single editor by numeric id' phrasing distinguishes it from list/search-style siblings and from get_artist/get_product by entity type, though it never explicitly contrasts with them.

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?

No guidance on when to use this versus alternatives. The phrase 'by their numeric id' implies an id from a prior call, but there is no statement of prerequisites, no note on how to obtain the id, and no mention of how it relates to list_events or the other get_* tools.

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