Skip to main content
Glama
Sign In
mcp-mat

mcp-mat

by codelipenghui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mat_oql_spec

Get OQL parser-mode guidance, supported patterns, and known limitations for Eclipse MAT queries.

Instructions

Return MAT OQL parser-mode guidance, supported patterns, and known limitations.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries full weight. It implies a read-only, informative operation, but does not detail any behavioral traits such as data source, caching, or error handling. Adequate but minimal.

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?

Single sentence, no fluff. Clearly conveys the purpose with front-loaded key terms. Every word 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?

Given zero parameters and no output schema, the description covers the purpose well. It specifies what is returned (guidance, patterns, limitations), which is sufficient for a spec tool. Minor improvement would be to mention the format of the output.

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?

No parameters exist in the schema, so schema coverage is 100%. The description adds no param info, which is fine. Baseline score 3.

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 returns MAT OQL parser-mode guidance, supported patterns, and known limitations, with a specific verb 'Return' and a distinct resource. It differentiates from sibling tools like mat_oql_query (which executes queries) and mat_parse_report.

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 like mat_oql_query or mat_parse_report. The description lacks context about prerequisites or typical usage scenarios, leaving the agent to infer.

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