List standards the catalogue covers
Every standard that has courses, with a course count each. Use this to discover valid values for the framework filter before searching. No authentication required.
200: Successful Response (Success Response) Content-Type: application/json
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden. It discloses 'No authentication required' and implies read-only behavior. However, it omits details like pagination, error responses, or whether data is live vs cached. More behavioral context would be helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core information is front-loaded in two sentences plus a brief authentication note. The 'Responses' section is slightly redundant but does not detract. It is concise without being under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple parameterless listing tool, the description is largely sufficient. However, given the absence of an output schema, it could be more complete by describing the exact response fields beyond just 'course count'. The structure of the returned objects is not fully clarified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, and schema description coverage is trivially 100%. According to rubric, zero parameters earn a baseline of 4. The description does not need to add parameter meaning, and it correctly focuses on purpose instead.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states 'List standards the catalogue covers' and clarifies it returns each standard with a course count. It distinguishes the tool as a discovery mechanism for framework filter values, which differentiates it from sibling search/retrieval tools like agent_search_frameworks or agent_get_framework.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description directly says 'Use this to discover valid values for the framework filter before searching.' This gives clear when-to-use guidance. It does not explicitly exclude alternatives, but the positive usage context is strong and sufficient given the sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Multiple tools cover overlapping crosswalk and coverage territory: agent_coverage_crosswalk, agent_coverage_report, agent_cross_framework_map, agent_crosswalk_pair, and agent_combined_coverage could all be chosen for similar questions. The near-duplicate agent_get_framework_controls and agent_get_framework_controls_by_name also creates avoidable ambiguity.
All tools share the agent_ prefix and snake_case style, but the grammatical pattern is mixed: many are verb_noun (agent_buy_crosswalk, agent_search_courses, agent_get_framework), while others are noun phrases or descriptive fragments (agent_capital_by_function, agent_combined_coverage, agent_controls_touched_by, agent_signals_this_week). The convention is readable but not uniform.
27 tools is above the 25-tool threshold and the set feels heavier than necessary because several crosswalk/coverage tools could be consolidated into a smaller family. The broad domain justifies variety, but the count is bloated by overlapping query surfaces and at least one redundant route.
The domain is well covered for a read-only compliance intelligence platform: framework discovery, control lookup, crosswalk analysis, course search, funding-signal exploration, and purchase-link generation are all present. Minor gaps exist, such as no direct way to inspect full control lists for arbitrary domains or retrieve mappings for a specific target control, but agents can generally work around them.
