Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

get_area

Read-only

One area: metadata, its dedicated site link, and a top sample of member providers (with the total). Use find_providers?area=slug for the full list, or view=full here. Results carry next: the sub-resources that exist for this entity and the exact tool call that retrieves each, computed from this record. Pass include_next=false to omit it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
viewNosummary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity).summary
limitNoTop members to show.
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.
include_nextNoSet false to omit the `next` affordance block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_next
      Added value: +{
+  "default": true,
+  "description": "Set false to omit the `next` affordance block.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 25,
+  "description": "Top members to show.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / view
      Added value: +{
+  "default": "summary",
+  "description": "summary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity).",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Although readOnlyHint=true already covers the safety profile, the description adds valuable behavior beyond annotations: the response carries a computed `next` block listing sub-resources and the exact tool call for each, and include_next=false suppresses it. It also discloses that only a top sample of providers is returned, with a total, which exceeds what the annotations alone imply.

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?

The description is three dense sentences with no filler: return composition, alternative tool routing, and the notable `next` behavior are covered and front-loaded. Every sentence earns its place.

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

Completeness5/5

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

Despite having no output schema, the description specifies the main return elements (metadata, site link, sampled providers, total, `next`) and the schema covers all parameters. Together they are sufficient for an agent to know what get_area returns, how to adjust the view, and when to switch to find_providers.

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 80%, so most parameters are already documented in the input schema. The description adds little beyond the schema: it alludes to slug via find_providers?area=slug and restates the include_next behavior, but view/limit/context are already fully described in the schema.

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?

The description immediately identifies the resource ('one area') and specifies the exact return shape: metadata, dedicated site link, and a top sample of member providers with their total. It also signals the main sibling difference by pointing to find_providers for the full list, so an agent can tell get_area from list-style tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an explicit routing rule: use find_providers?area=slug for the full list, or view=full here for the full record. The schema's view parameter further clarifies that get_api/get_provider should be used for a single entity, giving the agent clear when-to-use guidance.

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

All apis-io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources