Skip to main content
Glama

NEM Explorer (ScadaMiner)

get_writing_style

Read-onlyIdempotent

READ THIS BEFORE WRITING ANY ANALYSIS THAT WILL BE PUBLISHED — before the note or blocks you pass to share_artifact, and before any write-up, report, article or post the user will put their name on. Takes no arguments. Returns the house writing guide: how to avoid the constructions that make analysis read as machine-written, which NEM terms are real and which are invented, and the rule that every number must trace back to a query you actually ran. Cheap, and it is the difference between analysis a market professional trusts and analysis they dismiss on sight. Not needed for ordinary short chat answers.

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_writing_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_idNoOptional UUID returned by an earlier `start_question` call. When provided, this tool call is attributed to that question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 is covered. The description adds context the annotations cannot: that the call is argument-free, that it is inexpensive ('Cheap'), and roughly what the payload contains. The only omission is the return format (text vs structured), which keeps it off a 5.

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?

The imperative trigger is front-loaded and the exclusion is placed last, which is the right ordering. The persuasive line about trusted vs dismissed analysis is motivational rather than operational, but it is short and reinforces priority for a cheap call, so it mostly 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?

With no output schema, the description must convey what comes back, and it does so by listing the guide's subject areas, which is sufficient for a no-argument read-only fetch. Missing only the response format and whether the guide is versioned or cached.

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% and the schema itself explains `question_id` as an optional UUID from an earlier `start_question`. The description says only 'Takes no arguments,' which is slightly imprecise given the optional attribution parameter, so it neither compensates nor misleads — the schema does the work.

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 uses a specific verb and resource — 'Returns the house writing guide' — and then enumerates its contents: machine-written construction avoidance, which NEM terms are real vs invented, and the number-traceability rule. An agent immediately knows this is a static reference document fetch, not an analysis tool or a data query.

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?

It gives an explicit trigger ('READ THIS BEFORE WRITING ANY ANALYSIS THAT WILL BE PUBLISHED'), names the concrete sibling call point ('before the `note` or `blocks` you pass to `share_artifact`'), and states the exclusion ('Not needed for ordinary short chat answers'). Both the when and the when-not are spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.