Skip to main content
Glama

get_style

Read-only

Retrieve saved buyer style preferences and corrected draft feedback so replies and offers match the user's tone and wording.

Instructions

The buyer's saved preferences and the drafts they corrected (before, feedback, after). Follow them when writing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, so the description's added value is the disclosure that the result contains corrected drafts with before/feedback/after context. With no output schema present, that partial return-shape information is genuinely useful. It still doesn't say how large the result is, whether it can be empty for a new buyer, or how to weigh conflicting preferences.

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?

Two short sentences, front-loading what is returned before the instruction to apply it. Slightly cryptic pronoun usage ('them') and the unexpanded '(before, feedback, after)' tuple cost a bit of clarity, but there is no filler.

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?

For a no-parameter read with no output schema, the description should carry the return-value burden, and it only sketches it (preferences + corrected drafts in a three-part structure). An agent can call it correctly but cannot anticipate edge cases such as an empty style profile or conflicting saved preferences.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no input is needed, consistent with the empty schema.

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

Purpose4/5

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

The description names the specific resource returned: the buyer's saved preferences plus the drafts they corrected, with the before/feedback/after shape. That is distinctive enough to separate it from siblings like get_listing or get_negotiation. It lacks an explicit retrieval verb, but the content statement makes the purpose clear.

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

Usage Guidelines3/5

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

'Follow them when writing' implies the tool should be consulted before composing messages such as draft_message, which is real usage guidance. However, it gives no explicit when-not condition, no statement about calling order relative to draft_message/send_draft, and no note on whether the style must be refreshed per session.

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