Skip to main content
Glama

post_request

Publish a public requirement and maximum budget in free trial credits. Do not include confidential information. Does not create an order.

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": {
      "title": "<title>",
      "description": "<description>",
      "category": "<category>",
      "budget": "<budget>"
    },
    "name": "post_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesPublic service title
budgetYes
categoryYesCapability category
descriptionYesPublic description; do not include secrets

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 declare openWorldHint=true, readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the posting is public, the budget is denominated in free trial credits, and confidential information must be excluded. It does not say what happens after publishing (moderation, visibility, returned identifier).

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, front-loaded sentences with zero filler; the public-visibility constraint and the order-distinction each earn their place. Nothing is repeated verbatim from the schema.

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

Completeness3/5

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

The tool is simple (4 required scalar params, no output schema), and the description covers visibility, budget units and the non-order semantics. It omits what a successful call yields or what happens afterward, which matters because no output schema exists to fill that gap.

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 75% and the schema itself documents title, category and description. The description still adds meaningful semantics the schema lacks, notably that budget is measured in free trial credits, and reinforces that title/description become publicly visible. It does not explain the category values, which have no enum in the schema.

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 resource ('Publish a public requirement') and explicitly rules out the most likely confusion with create_order ('Does not create an order'), which separates it from a key sibling. It stops short of distinguishing itself from the other siblings such as search_requests or publish_service.

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 negation 'Does not create an order' implies the when-not case against create_order, which is useful routing. There is no positive statement of when to use this instead of create_order or publish_service, and no prerequisites or rate/eligibility context.

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