Skip to main content
Glama

Get style

mynahcast_get_style
Read-onlyIdempotent

Read one style (hook patterns, tone, caption style, length, slide count, colours, fonts, do/don't). Use its patterns as guidance for new, original posts; never reproduce a reference account's content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "styleId": "<styleId>"
    },
    "name": "mynahcast_get_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
toneYes
fontsYes
colorsYes
doListYes
brandIdYes
dontListYes
createdAtYes
isDefaultYes
updatedAtYes
postLengthYes
slideCountYes
captionStyleYes
hookPatternsYes
sourceReferenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's real addition is the licensing/usage constraint about not reproducing reference content — useful context, but nothing about misses, permissions, or error behavior beyond 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?

Two dense sentences: the first front-loads what is returned, the second front-loads the usage rule and its prohibition. No filler or restatement of the name.

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 an output schema present, the description needn't explain return shape, and its field enumeration still previews it well. Given annotations cover safety and the tool is a simple single-read, the only notable gap is not tying styleId back to a source (e.g., a style-listing call or an account).

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter, so the description carries the burden — and it only implies that "one style" is identified by a key, without stating that styleId is the UUID of a style as returned by a listing call. The meaning of the parameter is left entirely to the schema's format/pattern fields.

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 names a specific verb and resource ("Read one style") and immediately enumerates its contents — hook patterns, tone, caption style, length, slide count, colours, fonts, do/don't — so an agent knows exactly what a call yields. The singular "one style" also distinguishes it from a listing sibling.

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?

It gives a clear downstream use ("Use its patterns as guidance for new, original posts") plus a hard exclusion ("never reproduce a reference account's content"). No alternative tool is named for finding which style to read, but no inference about omitted siblings is required to call this correctly.

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.

Resources