Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

cohort_capabilities

Read-only

UNDERSTANDING — what every member of a cohort actually publishes: artifact counts by type plus the agent-readiness dimensions each one satisfies. The capability matrix behind a market report. Large cohorts come back in byte-budgeted chunks: while complete is false, call again with cursor set to next_cursor; the last page has complete: true and a null next_cursor. Priced B2 (cross-catalog synthesis) — $0.05 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
kindYesCohort kind: tag, industry, region, area or vc — says what `slug` names.
slugYesSlug of the cohort within `kind` — a tag, industry, region, area or VC slug, e.g. "payments" with kind "tag".
cursorNoResume offset from a previous response's next_cursor. Omit for the first page; keep calling while next_cursor is not null.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"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."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
  2. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"Cohort kind: tag, industry, region, area or vc — says what `slug` names."
    • addedInput schema / properties / slug / description
      Added value: +"Slug of the cohort within `kind` — a tag, industry, region, area or VC slug, e.g. \"payments\" with kind \"tag\"."
  3. 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"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Resume offset from a previous response's next_cursor. Omit for the first page; keep calling while next_cursor is not null.",
+  "minimum": 0,
+  "type": "integer"
+}
  5. Added

TDQS

A3.9/5.0
Behavior4/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 substantive behavior beyond that: byte-budgeted chunked pagination with the complete/next_cursor loop, and cost disclosure ($0.05/call, tier B2, included in Understanding/Influence). Auth requirements and rate limits remain unstated.

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-loads the purpose, then layers pagination and pricing. Every sentence is load-bearing, though the pricing sentence and 'See apis://prices' add bulk that could be trimmed for a description primarily used for selection.

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 carries the burden of explaining returns and does so partially: artifact counts by type, satisfaction dimensions, and the complete/next_cursor paging fields. It stops short of describing the shape of individual entries, but an agent has enough to call and iterate 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%, so the schema already documents kind, slug, cursor and context, including the enum values. The description reinforces the cursor/next_cursor paging contract but adds no meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb and resource: what members of a cohort publish — artifact counts by type plus the agent-readiness dimensions each satisfies. The 'capability matrix behind a market report' framing distinguishes it from siblings like cohort_scores, cohort_rankings and cohort_stats without needing to open any schema.

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?

Gives a usage context ('the capability matrix behind a market report') and detailed pagination instructions, but never explicitly contrasts with the many sibling cohort_* tools or states when NOT to use this one. Usage is implied rather than routed.

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