Coverage Cat

Coverage Cat docs resource reader

docs_get_resource

Read-onlyIdempotent

Read one Coverage Cat docs resource by URI from the default consumer MCP and return its URI, public href (null when it has no public page), MIME type, and full markdown, JSON, or YAML text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uri": "<uri>"
    },
    "name": "docs_get_resource"
  }
}

Input Schema

Name	Required	Description	Default
`uri`	Yes	A coveragecat:// or ui:// resource URI from docs_list_topics or docs_search.

Output Schema

Name	Required	Description
`uri`	Yes	The resource URI that was read.
`href`	Yes	Public web URL for the same content, or null when the resource has no public page.
`text`	Yes	The full resource body in mime_type format.
`mime_type`	Yes	Format of text, such as `text/markdown`, `application/json`, or `text/yaml`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

addedOutput schema / properties / href / description

Added value: +"Public web URL for the same content, or null when the resource has no public page."

addedOutput schema / properties / mime_type / description

Added value: +"Format of text, such as `text/markdown`, `application/json`, or `text/yaml`."

addedOutput schema / properties / text / description

Added value: +"The full resource body in mime_type format."

addedOutput schema / properties / uri / description
```
Added value: +"The resource URI that was read."
```

Changed1 schema field changedOct 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "href": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mime_type": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "uri": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "uri",
+    "href",
+    "mime_type",
+    "text"
+  ],
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety behavior is fully covered. The description adds useful context that href may be null and that content is returned in markdown/JSON/YAML, but does not discuss permissions, limits, or failure behavior beyond that.

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?

A single, front-loaded sentence with no filler; the action is stated first and the returned fields follow. Slightly dense but every clause earns its place.

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 one-parameter read tool with full annotation coverage and an output schema, the description is nearly sufficient. The remaining minor gap is the absence of guidance on what to do when a URI is unknown or invalid, which the output schema does not cover.

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% for the single parameter and the schema already documents the accepted 'coveragecat://' and 'ui://' URI forms and their origin. The description adds only 'by URI' and does not extend meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Read one Coverage Cat docs resource by URI') plus the source ('default consumer MCP'), which is clear. The singular 'one ... by URI' implicitly distinguishes it from docs_list_topics and docs_search, but it never names them, so differentiation is left to inference.

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?

The description implies usage (fetch a single resource once you have its URI), and the schema reinforces this by saying the URI comes from docs_list_topics or docs_search. However, there is no explicit when-to-use vs. sibling statement or precondition in the description itself.

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

All Coverage Cat tools Inspect

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

Need Help?