Skip to main content
Glama
Sign In

api-evangelist

by com.apievangelist
OverviewDiscussionsAdmin

find_areas

Read-only

The 77 focused topic areas of the network (agents, gateways, security, …), each a subsite with its own catalog.

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

B3.2/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 usefully discloses the fixed size of the result set (77) and that each area is a subsite with its own catalog, but says nothing about pagination behavior, default result shape, or cost of a call. Modest added value over the annotations.

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?

One compact sentence with the resource and its scope front-loaded and no filler. It earns its brevity, though it spends the whole sentence on what the entity is rather than what the call does.

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?

For a read-only, no-required-param listing tool with fully documented parameters and no output schema, the gaps are minor: the description does not sketch the fields a record returns (slug, title, url) even though the schema exposes a `fields` projection. An agent can still call it correctly.

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% across all 8 parameters (including enum values for sort and match and per-parameter defaults), so the schema carries the full semantic load. The description adds no parameter information, which is the expected baseline when the schema is this complete.

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 names the resource precisely and quantitatively ('The 77 focused topic areas of the network ... each a subsite with its own catalog'), so an agent knows what corpus is being enumerated. It supplies no verb of its own, however, and never contrasts itself with the sibling get_area (single-area retrieval), so the list-vs-fetch distinction is left to the tool name.

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 guidance, no prerequisite, and no mention of an alternative. Nothing tells the agent to reach for find_areas when it wants to browse or discover areas, versus get_area when it already has a slug.

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