Skip to main content
Glama

Score post authenticity

flypost_score_authenticity
Read-only

Score post text on the authenticity rubric (how human/authentic it reads — low scores risk LinkedIn throttling). Pass a draft_id or raw text. include_fixes: also return the ready-made fixes from the Post Score panel for the failing tips: rewrites ({find, replace}, find is an exact line of the post) or a question for the first-hand detail that is missing. Ask the user that question rather than inventing an answer.

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

Input Schema

NameRequiredDescriptionDefault
textNo
draft_idNo
include_fixesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and non-destructive behavior. The description adds meaningful context beyond that: the rubric's meaning, the LinkedIn throttling risk, the shape of include_fixes output (rewrites with {find, replace} or a question), and the instruction to ask the user rather than invent an answer.

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?

The description is front-loaded with the core purpose and risk, then moves into usage and include_fixes behavior. It is dense but mostly earns its space, though the include_fixes sentence is somewhat run-on.

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 read-only tool with no output schema, the description covers purpose, risk, parameter usage, and the include_fixes return shape. It does not describe the score output format or rubric details, but those gaps are minor for this tool's complexity.

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?

With 0% schema description coverage, the description carries the full parameter burden. It explains that draft_id or raw text may be passed and defines include_fixes behavior and return structure. It does not clarify precedence if both draft_id and text are supplied, nor whether one is required despite zero required parameters.

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 states a specific verb and resource: 'Score post text on the authenticity rubric,' and adds the consequence 'low scores risk LinkedIn throttling.' It does not explicitly differentiate from sibling tools, but no sibling appears to offer scoring, so the purpose is 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?

It tells the agent to 'Pass a draft_id or raw text' and explains when include_fixes applies, which gives basic invocation guidance. However, it provides no explicit when-not-to-use conditions or named alternatives among sibling tools.

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.