Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

find_conversations

Read-only

API Evangelist Conversations — recorded discussions with API practitioners (guest, company, YouTube/SoundCloud links).

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
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. Changed5 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."
  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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds no behavioral context beyond that. It says nothing about pagination behavior, result limits, or what the record shape looks like, which matters for an 8-parameter list tool.

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 compact sentence with no waste and the entity definition front-loaded. It is efficient, though it spends its one sentence on a definition rather than on the actionable information an agent needs.

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

Completeness2/5

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

For an 8-parameter, zero-required, open-ended retrieval tool with no output schema, the description should at minimum say what the tool returns and when to reach for it. It supplies only an entity gloss, leaving routing and return expectations unaddressed.

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 the schema already documents q, page, sort, tags, match, limit, fields, and context in detail. The description contributes no parameter meaning at all, which is the expected baseline-3 outcome when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

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

The description defines the resource ('recorded discussions with API practitioners') rather than stating the action the tool performs — there is no verb like find/search/filter, so the agent must infer the operation from the name. It does add useful domain grounding (guest, company, YouTube/SoundCloud links) that helps distinguish conversations from posts, videos, or papers. Overall the purpose is implied rather than stated.

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 guidance on when to use this tool versus siblings such as get_conversation (single record) or find_videos/find_posts (adjacent media types). No prerequisites, no exclusions, no query-vs-browse routing. The agent is left to guess the retrieval context entirely.

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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources