Skip to main content
Glama

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

curate

A recorded act on one drop: promoted · refused · withdrawn. A name AND a reason are always required — no anonymous judgement, and a refusal without a reason teaches the community nothing. WHO MAY ACT: promoting or refusing needs the steward token (these decide what the whole library amplifies); withdrawing your own card needs fields+signature from curate_signable instead. A typed name is not authority. A refusal withholds amplification only — the drop stays on the member's own shelf. Acts are appended, never replaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNosteward token — promote/refuse only
actionYes
fieldsNofrom curate_signable, to withdraw
reasonYes
card_idYes
stewardYes
signatureNodetached, over those fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / maxLength
      Added value: +4000
    • addedInput schema / properties / card_id / maxLength
      Added value: +4000
    • addedInput schema / properties / fields / additionalProperties
      Added value: +false
    • addedInput schema / properties / reason / maxLength
      Added value: +4000
    • addedInput schema / properties / signature / maxLength
      Added value: +4000
    • addedInput schema / properties / steward / maxLength
      Added value: +4000
    • addedInput schema / properties / token / maxLength
      Added value: +4000
  2. Changed3 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "from curate_signable, to withdraw",
+  "type": "object"
+}
    • addedInput schema / properties / signature
      Added value: +{
+  "description": "detached, over those fields",
+  "type": "string"
+}
    • addedInput schema / properties / token
      Added value: +{
+  "description": "steward token — promote/refuse only",
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that a name and reason are always required, that refusal only withholds amplification while the drop stays on the member's shelf, and that acts are appended never replaced. It also clarifies that typed names are not authority, which is important auth context.

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?

The description is dense and well-structured with clear sections (act types, requirements, who may act, consequences). Every sentence adds value, though phrases like 'teaches the community nothing' are slightly verbose and could be trimmed without losing meaning.

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?

Despite no annotations or output schema, the description covers the essential context: the meaning of each action, authentication requirements, the effect of a refusal, and the append-only persistence model. This is sufficient for an agent to understand when and how to use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 43%, but the description compensates by clarifying the token for promote/refuse, fields+signature for withdrawal, the action values (promoted/refused/withdrawn), and the universal requirement for reason. It adds meaning beyond the schema for the most nuanced parameters.

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?

The description clearly states that this tool records a curation act on a drop, enumerating the three possible actions: 'promoted', 'refused', and 'withdrawn'. It distinguishes itself from sibling tools like curate_queue and curate_signable by focusing on the act itself, not the queue or signing mechanism.

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?

The description explicitly explains who may act and what credentials are needed: promoting/refusing requires the steward token, while withdrawing requires fields+signature from curate_signable. It also warns that 'a typed name is not authority', setting expectations for when to use this tool. It doesn't name alternative tools explicitly but provides clear context.

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

All concordance toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources