Skip to main content
Glama
Sign In
bbaw-dse-mcp

bbaw-dse-mcp

by telota
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mop_get_biogramm_by_id

Fetch complete biographical entries by ID for detailed prosopographic data: family networks, career, possessions. Use after searching to get full structured information.

Instructions

Vollständiges Biogramm mit allen Details abrufen.

PURPOSE: Detaillierte biografische Daten einer Person abrufen

WHEN TO USE:

  • Nach search_biogramme() um Details zu bekommen

  • Um Familiennetzwerk, Karriere, Besitz zu analysieren

  • Für vollständige prosopographische Information

Args: biogramm_id: XML-ID des Biogramms (z.B. "P0005251") ctx: FastMCP Context

Returns: Dict mit allen biografischen Daten strukturiert

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": {
      "biogramm_id": "<biogramm_id>"
    },
    "name": "mop_get_biogramm_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
biogramm_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does not explicitly state read-only behavior or error handling, but the retrieval semantics are clear from 'abrufen'. It lacks disclosure of any potential side effects, permissions, or rate limits, though these are less critical for a get-by-ID operation.

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?

The description is well-structured with clear sections (PURPOSE, WHEN TO USE, Args, Returns). Every sentence earns its place, with no redundant information. It is concise yet informative, making it easy for an agent to parse.

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?

Given the tool's simplicity (one parameter, output schema present), the description covers purpose, usage, parameters, and return type. It lacks error-case behavior, but that is not required given the output schema's presence. The description is adequately complete for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has no description for biogramm_id (0% coverage), but the description compensates by defining it as an XML-ID and providing an example ('P0005251'). This adds meaningful semantics beyond the bare schema, though it doesn't explain how to discover the ID (e.g., from search results).

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

Purpose5/5

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

The description clearly states the tool retrieves a complete biography with all details, using the specific verb 'abrufen' and resource 'Biogramm'. It distinguishes itself from sibling tools like mop_search_biogramme by focusing on fetching by ID rather than searching, aligning with the tool name.

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

Usage Guidelines5/5

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

There is an explicit 'WHEN TO USE' section that tells the agent to use this tool after search_biogramme() to get details, and for analyzing family networks, careers, or possessions. It also names the alternative tool, providing clear context and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools