Skip to main content
Glama

The Valley Desk

Get one directory record

fetch
Read-onlyIdempotent

Get one publication, software project or clinical study by its directory id (from search or whats_new) or its thevalleydesk.org URL. Returns the regional connection and its source alongside kind-specific details.

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

NameRequiredDescriptionDefault
idYesDirectory id such as "doi:10.1000/example" or "474026", or the record's thevalleydesk.org URL.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesThe Valley Desk page for this record. Cite this URL.
textYesThe record as plain text.
titleYes
metadataYesThe record's fields, including kind, label and dates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description adds no permission or rate-limit notes. Its only behavioral contribution is the return shape ('regional connection and its source alongside kind-specific details'), which is partly redundant given an output schema exists.

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?

Two sentences, front-loaded with the core action and key forms, then the return summary. No filler or restated title text.

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?

For a single-parameter read tool with full annotations and an output schema, this covers purpose, key sources, and return contents adequately. Only not-found/error behavior is left unstated, a minor gap at this complexity.

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% and the single 'id' parameter already documents the DOI-style example and URL alternative that the description repeats. The description adds no format, validation, or lookup-failure semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and scope ('Get one') plus the enumerated resource kinds (publication, software project, clinical study) and the two accepted key forms (directory id or thevalleydesk.org URL). The 'one' framing and the reference to search/whats_new as id sources let an agent place it against the list-style siblings without opening any schema.

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 tells the agent where the required id comes from ('from search or whats_new') and that a thevalleydesk.org URL is an acceptable substitute, which is real routing guidance. It stops short of explicit exclusions such as 'do not use for bulk retrieval' or what happens when an id is not found.

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.