Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

search_api_evangelist

Read-only

Unified search across the whole network: 5k+ stories, 77 topic areas, 2.5k governance building blocks, papers, conversations, videos, tools, timelines, services, and vocabulary. Filter with types (posts, areas, guidance, rules, policies, standards, strategies, schema, properties, experiences, lifecycle, conversations, videos, papers, services, solutions, tools, timelines, vocabulary).

Input Schema

NameRequiredDescriptionDefault
qNoFree text over title, summary, tags, and body.
pageNoPage number, 1-based (default 1). Use with `limit` to walk a long list.
sortNoOrder when there is no `q`: "default" (dated content newest first, the rest A-Z), "title" (A-Z) or "date" (newest first). A `q` always orders by relevance.
tagsNoTag slugs; match any by default.
limitNoResults per page, 1-100 (default 25).
matchNoHow multiple `tags` combine: "any" (default, at least one) or "all" (every tag).any
typesNoContent types to include — plural resource names: posts, services, solutions, tools, areas, papers, videos, conversations, guidance, rules, policies, standards, strategies…, e.g. ["posts","papers"].
fieldsNoReturn only these keys on each record, e.g. ["slug","title","url"].
contextNoOptional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"Return only these keys on each record, e.g. [\"slug\",\"title\",\"url\"]."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1-100 (default 25)."
    • addedInput schema / properties / match / description
      Added value: +"How multiple `tags` combine: \"any\" (default, at least one) or \"all\" (every tag)."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-based (default 1). Use with `limit` to walk a long list."
    • addedInput schema / properties / sort / description
      Added value: +"Order when there is no `q`: \"default\" (dated content newest first, the rest A-Z), \"title\" (A-Z) or \"date\" (newest first). A `q` always orders by relevance."
    • addedInput schema / properties / types / description
      Added value: +"Content types to include — plural resource names: posts, services, solutions, tools, areas, papers, videos, conversations, guidance, rules, policies, standards, strategies…, e.g. [\"posts\",\"papers\"]."
  2. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful scope context (breadth of the corpus) but says nothing about result ordering across types, pagination limits, or truncation behavior beyond what the schema states.

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?

Front-loaded with the core purpose in sentence one. The second sentence is a long type enumeration that largely duplicates the schema's types description, costing some conciseness without being wasteful of the whole definition.

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 gives the agent a solid sense of scope and filterable types, and the schema covers all nine parameters and pagination. It is close to complete, missing only explicit routing versus sibling tools.

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%, so every parameter (q, page, sort, tags, limit, match, types, fields, context) is already documented. The description restates the types list, adding emphasis but no meaning 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (the whole network), and quantifies coverage (5k+ stories, 77 topic areas, 2.5k governance blocks). It does not, however, distinguish itself from the many per-type siblings (find_posts, find_papers, find_areas, etc.), so an agent must infer that this is the cross-cutting option.

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?

"Unified search across the whole network" implies this is the broad alternative to the per-type find_* tools, but the description never states when to prefer it over find_posts or get_post, nor any exclusions. Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All api-evangelist toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources