Skip to main content
Glama
Sign In
shapeless

shapeless

by ShapelessAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Approve posts

posts_approve
Destructive

Approve post proposals by ID to move them to the publishing schedule so they go out. Requires publish scope.

Instructions

PUBLISHES CONTENT: approving moves proposals to the schedule, and they will go out. Needs the publish scope.

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": {
      "ids": "<ids>"
    },
    "name": "posts_approve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesPost ids to approve.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the mutation profile is covered. The description adds value beyond them by stating the concrete consequence (content goes out) and the auth requirement ('Needs the publish scope'), which an agent could not infer from annotations alone.

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 short clauses, zero waste, and the irreversible consequence is placed first for maximum salience. Nothing needs trimming and nothing important is buried.

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?

With an output schema present, return values need not be described, and the auth scope plus publication consequence are covered. The only gap is absence of routing guidance relative to the closely named posts_publish sibling.

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?

Only one parameter, and schema description coverage is 100% ('Post ids to approve'), so the schema already carries the meaning. The description adds no extra semantics about id format, how many ids are accepted, or behavior of unknown ids, so the baseline 3 applies.

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?

States a specific verb and effect: approving moves proposals to the schedule and they will be published. The uppercase 'PUBLISHES CONTENT' front-loads the outcome clearly. It does not distinguish itself from the sibling posts_publish, which a reader may confuse with approval.

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?

The description implies when the tool applies (turning proposals into scheduled, outgoing content), which is useful context. But it names no alternatives such as posts_publish or posts_dismiss, and gives no explicit condition for choosing approval over dismissal or direct publishing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools