Skip to main content
Glama

List writing styles

list_writing_styles
Read-only

Use this when creating an AI-written campaign, to see the writing styles it can follow and to find one's id. Returns the organization's writing styles, the default first. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds behavior not in the annotations: the result set is scoped to the organization, the default style is ordered first, and the call is 'Free' (no credit consumption), which materially affects invocation decisions.

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 sentences with no filler: the when-to-use clause is front-loaded and the return characteristics follow. The phrase 'to find one's id' is slightly awkward but still communicates that the output carries identifiers for reuse.

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?

For a zero-parameter, non-destructive list tool with no output schema, the description covers when to call it, what it returns, ordering, and cost. Only the shape of the returned records (fields beyond the style id) is left unspecified, which is a minor gap given there is no output schema.

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 the baseline is 4. There is no parameter behavior the description needs to compensate for, and it does not waste space restating an 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 a specific resource and scope: the organization's writing styles, returned with the default first. The retrieval verb is implicit ('see ... writing styles') rather than stated as 'list', but an agent can immediately tell what the tool returns and that no other sibling tool covers writing styles.

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 trigger condition ('Use this when creating an AI-written campaign') and the downstream purpose ('to find one's id'), which tells the agent this is a lookup feeding a later call. There is no explicit when-not or named alternative, but no sibling appears to overlap with this resource.

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