Skip to main content
Glama

Policy: publish a version

policy_publish

Publish a policy (or a new version of one) by its document fingerprint. People then acknowledge that exact version. Requires the organization API key.

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": {
      "policy_id": "<policy_id>",
      "title": "<title>",
      "document_sha256": "<document_sha256>",
      "actor": "<actor>"
    },
    "name": "policy_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesWho is doing this (person or agent)
titleYes
policy_idYesYour short ID, e.g. acceptable-use
document_sha256YesSHA-256 fingerprint of the document (64 hex characters); the file stays with you

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the operation as a non-destructive, non-idempotent, open-world write. The description adds value beyond them by disclosing the organization API key requirement and the fingerprint-pinning model (each publish creates a version people acknowledge). It stops short of saying what happens on repeat publishes with the same fingerprint, which the non-idempotent hint leaves ambiguous.

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 sentences: what it does, why the fingerprint matters downstream, and the auth prerequisite. No filler, and the core action is front-loaded.

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 4-required-parameter mutation with no output schema, the description covers purpose, downstream effect, and auth. It leaves open the lifecycle edge cases (publishing over an existing version, whether policy_id must be new), which is a modest gap rather than a blocking one.

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 75%, so most parameters are self-documenting. The description still adds meaning by framing document_sha256 as the version identifier that acknowledgements bind to, which the schema's 'SHA-256 fingerprint' text does not convey.

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 policy or new version) plus the keying mechanism (document fingerprint). It implicitly distinguishes itself from policy_acknowledge by noting that acknowledgement happens afterward, though no sibling is named explicitly.

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 downstream-consequence sentence ('People then acknowledge that exact version') implies when publishing is appropriate, i.e., before an acknowledgement round. There is no explicit when-not guidance, such as what to do if the fingerprint already exists or how this relates to policy_status. Usage is implied rather than stated.

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