Skip to main content
Glama

Shape notes into post angles

shape_post

Turn rough notes about what the user did (shipped a feature, fixed a bug, hit a number) into 2-3 finished social-post angles in the user's voice. Grounded only in the notes - never invents facts. Uses one AI generation from the user's monthly quota.

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": {
      "notes": "<notes>"
    },
    "name": "shape_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYesRaw notes about what the user did. Rough is fine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the readOnly/openWorld/destructive profile, so the description's disclosure that this consumes 'one AI generation from the user's monthly quota' is genuinely additive cost information an agent needs before calling. The grounding guarantee ('never invents facts') also sets expectations. It stops short of saying whether the angles are returned as text or persisted as drafts, which is the one remaining behavioral gap.

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?

Three short sentences, front-loaded with the transformation, then the grounding constraint, then the cost caveat. No filler and no repetition of schema or annotation content.

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, but the description compensates by specifying the return shape ('2-3 finished social-post angles in the user's voice') and tone. For a single-parameter, non-destructive tool that is nearly sufficient; only the question of whether results are returned inline versus saved remains unaddressed.

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?

Schema coverage is 100% and the single parameter is well documented in-schema, so the baseline is met by structure alone. The description still adds value by characterizing what belongs in `notes` (raw activity notes, rough is fine, with concrete examples), reinforcing the schema's intent rather than restating its type/length constraints.

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?

Specific verb+resource+output: 'Turn rough notes ... into 2-3 finished social-post angles in the user's voice.' The input domain is concrete (shipped a feature, fixed a bug, hit a number) and the grounding constraint ('never invents facts') further pins down the transformation. An agent immediately knows what comes out, which also implicitly separates it from create_draft.

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?

Usage is implied by the input description ('rough notes about what the user did'), so the trigger condition is reasonably clear. However, no sibling is named despite create_draft being the obvious downstream step, and there is no statement of when-not to use this (e.g., when notes are already polished, or when the quota is exhausted).

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