SpecProof

Search Specifications

search_specifications

Read-onlyIdempotent

Search across 3GPP, IETF, and Multimedia specification documents using full-text search.

Args:
    query: Search query terms (required)
    doc_type: Filter by document type - "3gpp", "ietf", or "mpeg" (optional)
    spec_number: Filter by specification number (optional) 
    max_results: Maximum number of results to return (default: 10, max: 50)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`doc_type`	No
`max_results`	No
`spec_number`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedJul 9, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / doc_type / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / doc_type / default
```
Added value: +null
```
- removedInput schema / properties / doc_type / description
```
Removed value: -"Filter by document type (optional)"
```
- removedInput schema / properties / doc_type / enum
```
Removed value: -[
-  "3gpp",
-  "ietf",
-  "mpeg"
-]
```
- addedInput schema / properties / doc_type / title
```
Added value: +"Doc Type"
```
- removedInput schema / properties / doc_type / type
```
Removed value: -"string"
```
- removedInput schema / properties / max_results / description
```
Removed value: -"Maximum number of results"
```
- removedInput schema / properties / max_results / maximum
```
Removed value: -50
```
- removedInput schema / properties / max_results / minimum
```
Removed value: -1
```
- addedInput schema / properties / max_results / title
```
Added value: +"Max Results"
```
- removedInput schema / properties / query / description
```
Removed value: -"Search query terms"
```
- addedInput schema / properties / query / title
```
Added value: +"Query"
```
- addedInput schema / properties / spec_number / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / spec_number / default
```
Added value: +null
```
- removedInput schema / properties / spec_number / description
```
Removed value: -"Filter by specification number (optional)"
```
- addedInput schema / properties / spec_number / title
```
Added value: +"Spec Number"
```
- removedInput schema / properties / spec_number / type
```
Removed value: -"string"
```
- addedInput schema / title
```
Added value: +"search_specificationsArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "search_specificationsOutput",
+  "type": "object"
+}
```

Changed1 schema field changedJul 9, 2026

changedInput schema / properties / doc_type / enum

Previous value: -[
-  "3gpp",
-  "ietf"
-]New value: +[
+  "3gpp",
+  "ietf",
+  "mpeg"
+]

First observedFeb 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context such as full-text search capability and max_results limit (default 10, max 50). It does not detail output format, but an output schema exists to cover that.

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 concise and well-structured. It starts with a clear purpose statement, then provides a clean Args list. Every sentence adds value; no redundant or vague text.

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?

Given the tool's simplicity, strong annotations, and existing output schema, the description is complete. It fully explains the search scope, all parameters, and key constraints. There is no significant missing information for an agent to select and invoke the tool correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries full responsibility for explaining parameters. It succeeds by documenting all four parameters: query (required), doc_type with allowed values, spec_number, and max_results with default and maximum. This goes beyond the schema by adding meaningful constraints and semantics.

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 clearly states the tool searches across 3GPP, IETF, and Multimedia specification documents using full-text search. This specific verb+resource+scope effectively distinguishes it from sibling tools like semantic_search or list_documents.

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

Usage Guidelines4/5

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

The description provides clear context: use this tool when you need to perform a full-text search across these specific document repositories. It does not explicitly mention alternatives or exclusions, but the scope is well-defined. The detail on doc_type and spec_number filters helps the agent understand usage.

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

All SpecProof 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?