Skip to main content
Glama

Get writing voice

flypost_get_writing_voice
Read-only

Read the project writing voice (voice guide, avoid-words, formatting rules, LinkedIn copy instructions) and business context. Call this before writing any draft yourself.

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

Input Schema

NameRequiredDescriptionDefault
project_idNoProject (workspace) id. Omit to use the active project set with flypost_use_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/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 genuine value by naming the categories of content returned (voice guide, avoid-words, formatting rules, business context), though it says nothing about behavior when the project has no configured voice or whether output is cached/stale.

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 sentences, zero filler: the first defines the payload, the second defines the call timing. The enumeration of returned content is front-loaded and each sentence 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?

No output schema exists, and the description compensates by enumerating the return contents, which is the key thing an agent needs in order to know this is the right source of style constraints. It is missing only edge-case behavior (unset voice, fallback to business context only), a minor gap for a single-parameter read.

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?

There is one optional parameter (project_id) with 100% schema description coverage that already explains omitting it falls back to the active project set via flypost_use_project. The description adds no parameter meaning of its own, but the schema fully carries that burden, making the baseline 3 correct.

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?

States a specific verb (read) and resource (project writing voice) and enumerates exactly what it returns: voice guide, avoid-words, formatting rules, LinkedIn copy instructions, and business context. The verb 'read' alone distinguishes it from the sibling flypost_update_writing_voice without needing to name it.

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?

Gives an explicit trigger condition: 'Call this before writing any draft yourself,' which tells the agent exactly when this tool belongs in a sequence. It stops short of naming the write-side alternative (update_writing_voice) or stating any when-not-to-use case, so it is clear context rather than full routing guidance.

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.