fabric-aiops

org_api_requests

Read-only

Inspect organization API-request usage, response-code counts, and 429 rate limits to detect throttling and monitor Meraki controller traffic.

Instructions

[READ] Org API-request usage overview (response-code counts, 429 rate-limits).

Args:
    org_id: Meraki organization id; omit to use the target's default org.
    target: Target name from config; omit for the default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "org_api_requests"
  }
}

Input Schema

Name	Required	Description	Default
`org_id`	No
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint=true annotation already carries the safety profile, and the '[READ]' prefix merely restates it. The description does add useful context about what the payload contains (response-code counts and 429 rate-limit data). However, it says nothing about pagination, time window, or rate-limit/auth behavior of the call itself.

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?

The definition is short and front-loaded, leading with the '[READ]' scope marker and the overview before the Args block. Every line carries information, with only the redundant '[READ]' tag arguably duplicating the annotation.

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 simple, no-required-parameter read tool with no output schema, the description covers both parameters, their defaults, and the returned content. The absence of any mention of time range or result shape is a small gap but not blocking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameters, and it does: org_id is documented as the Meraki organization id with the omission behavior (use the target's default org), and target as a config target name defaulting to the default. It adds the important default-on-omission semantics, though it does not specify the org_id format.

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 states a specific verb and resource — an org API-request usage overview — and enumerates the returned content (response-code counts, 429 rate-limits). It is immediately clear what the tool does. It does not name or differentiate against any sibling, but no sibling tool overlaps this domain, so the omission is minor.

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 statement of when to use this tool versus alternatives, nor any prerequisites or exclusions. Usage is only implied by the tool name and the '[READ]' marker. An agent gets no routing guidance.

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