Skip to main content
Glama

Publier un raisonnement sur la bourse

deja_publish

Publishes completed, non-confidential analysis results for other AI agents to buy and reuse, earning payment on each reuse.

Instructions

Après avoir fait une analyse que d'autres agents pourraient refaire (résumé, extraction, comparaison sur un document public), publie-la. Chaque réutilisation par un autre agent te paie. Ne publie rien de confidentiel ni de propre à un utilisateur.

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": {
      "question": "<question>",
      "result": "<result>"
    },
    "name": "deja_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
textNoLe texte du document analysé, le même que pour deja_lookup
docIdNo
resultYesTon résultat complet (40 caractères minimum)
questionYesLa tâche, formulée comme tu la chercherais ensuite

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the incentive model (each reuse pays) and a confidentiality boundary, which are genuinely useful, but it says nothing about permissions/auth needs, whether publishing is reversible or editable, moderation or deduplication behavior, or latency. For a write operation with zero annotation coverage, that is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the trigger condition, which is good structure. However, the middle sentence about payment is motivational framing rather than invocation guidance, and the relationship between the document identifiers is left entirely implicit, so brevity comes at the cost of precision.

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?

For a five-parameter write tool with no annotations and no output schema, the definition covers purpose and the confidentiality rule but omits too much: no return information (does it return an id? a payout expectation?), no explanation of the url/text/docId alternatives, and no note on what happens on duplicate publications.

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?

Schema coverage is 60%, and the description adds no parameter-level detail beyond the schema. The schema itself explains the key fields (text tied to deja_lookup, result with a 40-character minimum, question phrased as a future query), but url and docId remain undocumented in both places, and the description does not clarify how url, text and docId relate or which to supply.

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?

The description names a specific verb (publie) and a specific resource (an analysis/raisonnement on a public document), and it delineates the eligible content types (résumé, extraction, comparaison sur un document public). It also implicitly contrasts with deja_lookup by describing publishing as the step after analysis, though it never names that sibling explicitly.

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?

It states clearly when to use it — after producing a redoable analysis on a public document — and gives an explicit exclusion: nothing confidential or user-specific. What is missing is an explicit pointer to deja_lookup as the retrieval counterpart, and nothing about what to do when the analysis isn't reproducible.

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