Skip to main content
Glama

Tulsa Ecosystem Map

Browse a category

get_category
Read-onlyIdempotent

List a category's entries, Tulsa entries first, with page citations and entryClass on each member. typeTabs shows the available type pages and their full entry counts.

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

Input Schema

NameRequiredDescriptionDefault
idYesA category id from list_categories, e.g. 'fundraising'.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real behavioral detail beyond them: result ordering, page citations and entryClass per member, plus a typeTabs structure with full counts. It still leaves pagination behavior and the meaning of 'Tulsa entries first' unexplained.

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?

Two tightly written sentences, front-loaded with the core action and output shape. The only friction is the unexplained term 'Tulsa entries first', which costs the reader a beat.

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 two-parameter read with no output schema, the description gives a usable sketch of the return payload (citations, entryClass, typeTabs counts). The main gap is the absence of any paging guidance despite a limit parameter capped at 300.

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

Parameters2/5

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

Schema coverage is only 50%: id is documented in the schema, but limit has no description and the prose never mentions it, so nothing compensates for the gap. The description adds no meaning about page size or how limit interacts with the cited pages.

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 a specific verb and resource ('List a category's entries') and adds scope details (ordering, per-member fields). It is clearly distinct from list_categories, though it never names that sibling explicitly.

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?

Usage is only implied: browse a category once you have an id. There is no explicit statement of when to use this versus list_categories, get_entry, or search_entries, and no when-not guidance.

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