rocketmatter-mcp

by RosenAdvertising

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_new_matter_defaults

Retrieve default configurations for new legal matters. Fails with clear errors if defaults are missing.

Instructions

[Not in LCS /v1] New-matter defaults lookup. Fails loudly.

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": "get_new_matter_defaults"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jul 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Fails loudly,' which indicates it will throw errors clearly, but does not disclose whether it is a read-only operation, any side effects, or what success looks like. More behavioral detail is needed for a safe agent invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), but the inclusion of '[Not in LCS /v1]' is unnecessary for an agent and wastes space. It is front-loaded with the purpose, but the overall terseness borders on under-specification. Every word should earn its place, and this one does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and an output schema exists, the description is minimally complete. However, it does not clarify what 'defaults' refers to or how the output is structured. The 'Fails loudly' note adds a hint, but the overall context is sparse for a lookup tool that might be used in decision-making.

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?

The input schema has zero parameters, so schema description coverage is effectively 100%. The description adds no parameter information, which is acceptable since there are none. Baseline score of 3 applies as the schema does not require additional explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'New-matter defaults lookup' which clearly identifies the resource and operation. However, the prefix '[Not in LCS /v1]' is confusing and may mislead the agent about its availability. No explicit verb like 'get' is used, but 'lookup' implies reading. It distinguishes from siblings like 'get_new_matter_definition' but not explicitly.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use, or related tools. The description simply states the purpose without any usage context.

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

Deploy Server