Skip to main content
Glama

Tulsa Ecosystem Map

Read an entry

get_entry
Read-onlyIdempotent

Get an entry by id, with its definition, example, funding evidence, official site, public connections, source URLs and map citation.

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

Input Schema

NameRequiredDescriptionDefault
idYesAn entry id from search_entries, e.g. 'techlahoma'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds value by enumerating what is returned (definition, example, funding evidence, official site, connections, sources, map citation), which substitutes for the absent output schema. It does not describe behavior for a nonexistent id or any error/pagination behavior.

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 the verb and resource first, followed by the return payload; no filler or repetition. The field enumeration is dense but each item is informative given there is no output schema.

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 no output schema, the description covers the return contents and the schema covers the id format, which is nearly everything an agent needs. Only the failure case for an unknown id is left unstated.

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 parameter is fully documented in the schema with a concrete example ('techlahoma'). The description adds nothing beyond 'by id', so the schema does the heavy lifting and 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 ('Get an entry by id') and enumerates the returned content, which clearly separates it from the list_*/get_category/get_kind/get_tag siblings that operate on other resources. It never names search_entries as the feeder tool, but the resource itself is distinct enough to identify the tool.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use statement appears in the description; usage is only implied. The input schema's parameter text ('An entry id from search_entries') does hint at the search-then-fetch workflow, which is why this is not a 2.

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