Skip to main content
Glama

Tulsa Ecosystem Map

Browse a kind

get_kind
Read-onlyIdempotent

List entries of one kind, Tulsa entries first, with summaries and page citations for the list and its entries.

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

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "investor",
      -  "organization",
      -  "nonprofit",
      -  "program",
      -  "school",
      -  "government"
      -]New value: +[
      +  "investor",
      +  "organization",
      +  "nonprofit",
      +  "faith-community",
      +  "program",
      +  "school",
      +  "government"
      +]
  2. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: result ordering (Tulsa entries first) and return contents (summaries plus page citations for the list and each entry). It says nothing about what happens when the result set exceeds the limit or how pagination/truncation works, which matters given a default of 50 and max of 300.

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?

A single sentence with the action front-loaded and no padding. The 'Tulsa entries first' fragment is slightly cryptic and interrupts the otherwise clean list-then-return structure, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does useful work by describing return contents, and annotations cover the safety profile. However, for a tool with a bounded 'limit' parameter and a fixed enum of kind ids, the absence of any paging or enum explanation leaves a real gap for correct invocation.

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 description coverage is 0%, so the description is the only place parameter meaning could be added, and it adds none. It never explains that 'id' must be one of seven enumerated kind values or what 'limit' controls (page size vs total returned). The vague 'one kind' phrasing is the only hint at the id parameter.

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 states a specific verb and resource: list entries belonging to one kind, returning summaries and page citations. That clearly separates it from list_kinds (which enumerates kinds) and get_entry (single record), though it never names those siblings explicitly. The odd 'Tulsa entries first' clause adds scope flavor without obscuring the core action.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of the obvious alternatives (search_entries for filtered discovery, get_entry for a single record, list_kinds for the catalog). An agent must infer from the name alone that this is the browse-by-kind path. Usage is only implied by the phrase 'List entries of one kind'.

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