Skip to main content
Glama

Tulsa Ecosystem Map

Search the map

search_entries
Read-onlyIdempotent

Search Tulsa Ecosystem Map entries by name, alias or rough spelling. Matches include a summary, page citation and id for get_entry.

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": {
      "query": "<query>"
    },
    "name": "search_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNoOnly entries of all these kinds, e.g. ['investor'].
limitNo
queryYesWords to look for, e.g. 'SAFE note' or 'venture studio'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kinds / items / enum
      Previous value: -[
      -  "concept",
      -  "tool",
      -  "organization",
      -  "investor",
      -  "user-group",
      -  "nonprofit",
      -  "program",
      -  "place",
      -  "school",
      -  "government"
      -]New value: +[
      +  "concept",
      +  "tool",
      +  "organization",
      +  "investor",
      +  "user-group",
      +  "nonprofit",
      +  "faith-community",
      +  "program",
      +  "place",
      +  "school",
      +  "government"
      +]
  2. First observed

TDQS

A4.2/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, non-destructive, closed-world), so the description's main job is to add context — which it does by disclosing fuzzy/alias matching and describing the shape of each match. It stops short of ranking order, result volume, or what happens on zero matches.

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 tight sentences with zero waste: purpose and matching behavior first, then the return payload and the natural next call. Nothing to cut.

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?

With no output schema, the description usefully enumerates what each match contains (summary, citation, id) and how to continue to get_entry. It falls short only on result-volume and filtering behavior (limit, kinds), which an agent would want before issuing broad queries.

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 coverage is 67%, so the schema already explains query and kinds. The description meaningfully refines query semantics to include alias and rough-spelling matching, but says nothing about the kinds filter or the limit parameter (default 10, max 50) that controls result size. Baseline 3 is right when the schema carries most of the load.

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 (Search) and resource (Tulsa Ecosystem Map entries) plus the matching modes (name, alias, rough spelling). It also names the follow-up tool get_entry, so an agent can tell this apart from the retrieval siblings without opening a 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?

Usage context is clear: search when you have approximate knowledge of a name or spelling, then call get_entry using the returned id. What's missing is any exclusion — nothing says to prefer list_kinds/list_tags for enumeration or get_entry when the id is already known.

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