Skip to main content
Glama

Record a submission

record_submission
Idempotent

Records what happened at a directory, on the dashboard. submitted: sent (with the confirmation URL, and the listing URL once the directory shows one). draft: saved there but not sent yet (say what is left in note). needs_human: waiting on the user. rejected, skipped (take it off the plan). Never records live: verify_link does that after reading the public page.

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": {
      "directory": "<directory>",
      "status": "<status>"
    },
    "name": "record_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoWhat is left or what came back.
routeNofree, or paid when a fee or paid plan was used.
statusYes
productNoThe product's website or name. Leave empty for the product last worked on (list_products shows them).
directoryYesThe directory's slug.
listing_urlNoThe public listing page, when the directory shows one. This is the page link checks open.
confirmation_urlNoThe directory's thanks or confirmation page: proof it was sent. Never checked for a link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description explains crucial behavioral context regarding URL requirements: distinguishing between needing a confirmation URL (for submitted status) and a listing URL (when the directory shows one). This adds value beyond the schema details.

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?

The description is slightly dense and delivered in one block of text. While all information is present, it could be improved by using a bulleted list for the status types to enhance structure.

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?

The description is highly complete for a status-tracking tool. It covers the lifecycle of a submission (draft -> submitted -> rejected/skipped) and defines the expected data inputs for those states.

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?

Given the 86% schema coverage, the description adds semantic value by explaining the meaning and specific inputs required for the complex `status` enum and how URLs relate to different operational states.

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 purpose is clear: recording what happened at a directory and assigning a status. It uses distinct status types (draft, submitted, rejected) to differentiate its function from mere listing tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool provides excellent usage guidance by specifying boundary conditions, such as noting that `verify_link` is the tool used for live verification, which prevents misuse.

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.