Skip to main content
Glama

Fiche d’un architecte

get_architect
Read-onlyIdempotent

Architecte : variantes de nom, dates, identifiants (Wikidata, inventaire flamand), biographie vérifiée si elle existe, liste de ses œuvres dans le corpus.

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_architect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant (ex. victor-horta) ou nom
langNoLangue des textes renvoyés (fr fait foi)fr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds return-shape context the annotations cannot: that the biography is only present when verified, and which external identifier systems (Wikidata, inventaire flamand) may appear. It stops short of describing error/not-found behavior.

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 sentence built as a front-loaded noun-phrase list of the resource and its returned fields, with no filler or repetition. Every clause contributes distinct information.

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 output schema, the description correctly carries the return-value burden by enumerating the record's fields, and the annotations cover the safety profile for this read-only lookup. The remaining gap is routing guidance relative to search_architects and not-found behavior, which keeps it below 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 description coverage is 100%, so id (with example 'victor-horta') and the lang enum with its 'fr fait foi' note are fully documented in the schema. The description adds nothing about parameter behavior or how lang interacts with the returned name variants, so the 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?

The description names the resource (an architect record) and enumerates its contents: name variants, dates, Wikidata/Flemish-inventory identifiers, verified biography, and works in the corpus. That is enough for an agent to know what it retrieves, but it never states the verb operation and never distinguishes itself from the sibling search_architects, which serves the same domain.

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 when-to-use statement, no mention of when to prefer this over search_architects, and no note on what to do when the given id yields nothing. Usage is only inferable from the required id parameter, so the description provides no guidance of 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