Dinilu Deutschland — bedruckte Werbeartikel

Fetch

fetch

Compatibility fetch for research clients that require a tool named "fetch". Returns one product as readable text. It carries NO price: prices depend on quantity and options and come from get_quote.

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": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The id returned by search (the product mpn, as a string).

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`content`	No
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the tool returns one product as readable text and that it carries no price, which is useful. However, it does not explicitly state that it is a read-only operation, nor does it mention any side effects, error behavior, or authentication requirements. The description is adequate for a simple fetch but lacks depth.

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 two sentences, front-loading the core purpose and then adding the important price caveat. Every sentence earns its place, with no redundancy or fluff.

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?

The tool is simple: one parameter, an output schema, and clear compatibility context. The description covers the essential purpose, the price exclusion, and the compatibility scenario. It does not explicitly mention when not to use it versus get_product, but given the simplicity and presence of an output schema, it is sufficiently complete for an agent to call it correctly.

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 the baseline is 3. The description does not add any extra meaning to the id parameter beyond what the schema already provides, which is acceptable given that the schema fully describes it.

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 clearly states the verb 'fetch' and the resource 'one product as readable text', and notes it is a compatibility tool for research clients. It distinguishes itself from get_quote by explicitly stating it carries no price, but it does not differentiate from the sibling get_product, leaving some ambiguity about when to prefer this over that tool.

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

Usage Guidelines4/5

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

It provides a clear condition for use (research clients requiring a tool named 'fetch') and explicitly tells users that prices come from get_quote, implying this tool should not be used for pricing. However, it does not mention any alternative such as get_product, so the guidance is partial.

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

All Dinilu Deutschland — bedruckte Werbeartikel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?