Skip to main content
Glama

Score Draft

score_draft
Read-onlyIdempotent

[Read · free] Predict how a draft post will perform against the user's historical data. Uses an OLS regression model with detrending, ridge regularization, and recency weighting — the same model used on the /score page. Returns a predicted engagement percentile, projected engagement range, factor breakdown, similar past posts, and improvement suggestions. Free. Pass profile_id to scope to a tracked profile, collection_id to scope to a collection, or neither to score against the user's full library.

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": {
      "text": "<text>",
      "day_of_week": "<day_of_week>",
      "hour": "<hour>"
    },
    "name": "score_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
hourYesPlanned hour (0-23, UTC)
textYesDraft post text
formatNoPost format: text, image, video, document, article, or polltext
profile_idNoOptional tracked profile ID (scopes the model to this profile's posts)
day_of_weekYesPlanned day of week (0=Sunday, 6=Saturday, UTC)
collection_idNoOptional post_collections.id (scopes the model to this collection)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds value beyond that by disclosing the model internals (OLS with detrending, ridge regularization, recency weighting), the fact that it mirrors the /score page, and the cost ('free'). It does not mention latency, failure modes, or behavior with insufficient history.

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?

Front-loaded with a '[Read · free]' tag and a one-line purpose, then scope guidance last — a good order. The word 'Free' is stated twice ('free' in the tag and 'Free.' mid-paragraph), which is minor waste in an otherwise dense, information-rich definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: predicted percentile, engagement range, factor breakdown, similar past posts, and suggestions. Combined with the three required parameters being fully described in the schema, an agent has everything needed to call this correctly.

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%, so baseline is 3, but the description adds real meaning: it explains that profile_id and collection_id are scope selectors and that omitting both falls back to the user's full library. That interaction between parameters is not stated in the schema and prevents a mis-scoped call.

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 and resource ('Predict how a draft post will perform against the user's historical data') plus the exact model used and what it returns. An agent can immediately tell this is a scoring/prediction tool, distinct from sibling retrieval tools like get_posts or find_similar_posts.

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 concrete scoping rules: pass profile_id to scope to a tracked profile, collection_id for a collection, or neither for the full library. It also flags the call as free, which matters for an agent deciding whether to invoke it. It stops short of naming alternatives or stating when not to use it.

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