api-evangelist

find_services

Read-only

The services API Evangelist offers teams and customers — API strategy, governance, discovery, and evangelism engagements by Kin Lane. The front door to working with API Evangelist. (For the third-party vendor registry, use find_solutions.)

Input Schema

Name	Required	Description	Default
`q`	No	Free text over title, summary, tags, and body.
`page`	No	Page number, 1-based (default 1). Use with `limit` to walk a long list.
`sort`	No	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.
`tags`	No	Tag slugs; match any by default.
`limit`	No	Results per page, 1-100 (default 25).
`match`	No	How multiple `tags` combine: "any" (default, at least one) or "all" (every tag).	any
`fields`	No	Return only these keys on each record, e.g. ["slug","title","url"].
`context`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026

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

Changed1 schema field changedOct 19, 2026

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

Changed1 schema field changedJul 2, 2026

removedInput schema / properties / party

Removed value: -{
-  "default": "first",
-  "enum": [
-    "first",
-    "third"
-  ],
-  "type": "string"
-}

First observedJul 2, 2026

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 safety is covered. The description adds content-scope context (what kinds of engagements exist) but says nothing about result volume, pagination, or how a 'service' record differs from a paper/post record — useful behavioral detail it could have carried.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It leads with the content scope, which is good front-loading, and the sibling routing note is valuable. But 'The front door to working with API Evangelist' is pure marketing filler that consumes space without helping an agent decide or invoke.

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?

For an 8-parameter, no-required-args search tool with 100% schema coverage and no output schema, the description is adequate but thin: it never describes what a returned record contains or how paging/sorting interact at a practical level. The safety profile is left entirely to annotations.

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%, including detailed notes on q, sort, match, and context, so the schema does the heavy lifting. The description adds no syntax or semantics beyond the schema, which is the correct baseline of 3 when coverage is this high.

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?

It names the resource (services API Evangelist offers) and enumerates the engagement types — API strategy, governance, discovery, evangelism — so an agent knows what records this covers. It also explicitly contrasts with find_solutions for the third-party vendor registry. However, it frames itself as 'the front door to working with API Evangelist,' which is promotional rather than stating the operation (search/listing over service records).

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?

The parenthetical gives one explicit routing rule: use find_solutions for the third-party vendor registry. That excludes the most confusable sibling. Beyond that single case it offers no guidance on when to prefer this over find_posts, find_tools, or find_conversations, so it stops short of full when/when-not coverage.

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

All api-evangelist tools Inspect

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

Need Help?