Skip to main content
Glama
Sign In
rocketmatter-mcp

rocketmatter-mcp

by RosenAdvertising
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_firm_summary

Retrieve firm financial summary including account balances, overdue amounts, and retainer information for RocketMatter.

Instructions

[Not in LCS /v1] Firm financial summary (balances, overdue, retainers) is not exposed by /v1; 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_firm_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Without any annotations, the description fully discloses the behavioral trait: calling this tool results in a failure. This is completely transparent.

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 extremely concise (one sentence) with the most critical information (non-availability and failure) placed at the front.

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 that there is an output schema (presumably documenting the intended structure) and no parameters, the description effectively communicates the tool's unavailability and the reason, which is sufficient for this stub function.

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?

There are no parameters, so the baseline is 4. The description adds no parameter info, but none is needed.

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 intended purpose (firm financial summary with balances, overdue, retainers) and explicitly notes that it is not available in the current version, making its role as a non-functional stub unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states that the tool 'fails loudly' and is '[Not in LCS /v1]', effectively instructing the agent not to use it because it will not succeed.

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

Deploy Server

Other Tools