Skip to main content
Glama

create_policy

Create a custom ToS risk policy owned by your API key — your principal's own dealbreakers. block_categories veto a vendor (verdict BLOCK); flag_categories mark findings for review (verdict FLAG). Categories come from the 21-category taxonomy, e.g. binding_arbitration, data_training_use, data_sharing_resale, auto_renewal, unilateral_price_change. Use list_policies to see ids.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionNo
flag_categoriesNo
block_categoriesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the downstream effect of each field (verdicts BLOCK/FLAG) and the 21-category taxonomy, but says nothing about authorization requirements, whether the policy applies automatically to future scans, policy-count limits, or whether creation is reversible.

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?

Three tight sentences, front-loaded with the purpose before the field semantics and the cross-reference. No filler, though the taxonomy examples are dense inline rather than structured.

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?

An output schema exists, so return values need not be explained. For a 4-parameter write tool with no annotations and zero schema coverage, the description covers the decision-relevant semantics well; only permissions and policy application behavior remain unspecified.

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 description coverage is 0%, so the description must compensate, and it does for the two non-obvious fields: it defines block_categories versus flag_categories and supplies concrete example taxonomy values (binding_arbitration, data_training_use, etc.) that act as the missing enum documentation. The name and description parameters are left unaddressed, though both are largely self-explanatory.

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 ("Create a custom ToS risk policy") and scopes ownership ("owned by your API key — your principal's own dealbreakers"). It is clearly distinguishable from list_policies, which it names as the read counterpart.

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?

Explains the operative choice between the two category types: block_categories veto a vendor (BLOCK) versus flag_categories mark for review (FLAG), which tells an agent how to use the tool. It also points to list_policies for ids, but gives no explicit when-not guidance or prerequisites such as required scopes.

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.