Skip to main content
Glama
pulse-verity

pulse-verity

Submit Verity Feedback

submit_verity_feedback
Idempotent

Report a reproducible Verity API or MCP bug, missing capability or data-quality issue for human review so you get a tracking receipt once the private report is stored.

Instructions

Submit a reproducible Verity API or MCP bug, missing capability or data-quality report for human review. Requires a developer key (PULSE_API_KEY) or the hosted server, and an enabled feedback service. Include the failed call's requestId when available. Do not send secrets, personal information or conversation transcripts. Saves a private report; does not change prices, start trades or open or merge a PR. Returns a tracking receipt only after storage succeeds.

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": {
      "category": "<category>",
      "surface": "<surface>",
      "expected": "<expected>",
      "actual": "<actual>",
      "reproduction": "<reproduction>"
    },
    "name": "submit_verity_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
actualYesWhat actually happened
symbolNoCrypto ticker the report is about, when there is one
surfaceYesThe tool or API route the report is about
categoryYesKind of report: bug, missing_capability or data_quality
expectedYesWhat you expected to happen
requestIdNorequestId from the response you are reporting, when you have it
observedAtNoWhen you saw the problem (ISO-8601 with offset)
reproductionYesSteps to reproduce, 1 to 6 short lines

Output Schema

NameRequiredDescriptionDefault
errorNo
successNo
feedbackNo
duplicateNo
requestIdYesIdentifier for this MCP call; not a signed price field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.3.7
    • addedInput schema / properties / actual / description
      Added value: +"What actually happened"
    • addedInput schema / properties / category / description
      Added value: +"Kind of report: bug, missing_capability or data_quality"
    • addedInput schema / properties / expected / description
      Added value: +"What you expected to happen"
    • addedInput schema / properties / observedAt / description
      Added value: +"When you saw the problem (ISO-8601 with offset)"
    • addedInput schema / properties / observedAt / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • addedInput schema / properties / reproduction / description
      Added value: +"Steps to reproduce, 1 to 6 short lines"
    • addedInput schema / properties / requestId / description
      Added value: +"requestId from the response you are reporting, when you have it"
    • addedInput schema / properties / surface / description
      Added value: +"The tool or API route the report is about"
    • addedInput schema / properties / symbol / description
      Added value: +"Crypto ticker the report is about, when there is one"
    • addedOutput schema / properties / feedback / properties / expiresAt / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • addedOutput schema / properties / feedback / properties / receivedAt / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • addedOutput schema / properties / feedback / properties / updatedAt / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • addedOutput schema / properties / requestId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. Changed4 schema fields changedv1.3.6
    • changedInput schema / properties / surface / enum
      Previous value: -[
      -  "get_index_price",
      -  "get_index_batch",
      -  "list_index_assets",
      -  "get_settlement_print",
      -  "verify_print",
      -  "/api/index/v1/price",
      -  "/api/index/v1/batch",
      -  "/api/index/v1/print",
      -  "/api/index/v1/verity/catalog",
      -  "/api/index/v1/pubkey",
      -  "/api/index/v1/sample",
      -  "/api/index/v1/history",
      -  "/api/index/v1/metadata",
      -  "/api/index/v1/research/compare",
      -  "/api/index/v1/source-health",
      -  "/api/index/v1/verity/price",
      -  "/api/index/v1/verity/batch",
      -  "/api/index/mcp"
      -]New value: +[
      +  "get_index_price",
      +  "get_index_batch",
      +  "list_index_assets",
      +  "get_recorded_print",
      +  "get_settlement_print",
      +  "verify_print",
      +  "/api/index/v1/price",
      +  "/api/index/v1/batch",
      +  "/api/index/v1/print",
      +  "/api/index/v1/verity/catalog",
      +  "/api/index/v1/pubkey",
      +  "/api/index/v1/sample",
      +  "/api/index/v1/history",
      +  "/api/index/v1/metadata",
      +  "/api/index/v1/research/compare",
      +  "/api/index/v1/source-health",
      +  "/api/index/v1/verity/price",
      +  "/api/index/v1/verity/batch",
      +  "/api/index/mcp"
      +]
    • addedOutput schema / properties / error / properties / batchLimit
      Added value: +{
      +  "maximum": 100000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / error / properties / plan
      Added value: +{
      +  "enum": [
      +    "Developer",
      +    "Basic",
      +    "Builder",
      +    "Commercial",
      +    "Enterprise"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / error / properties / requested
      Added value: +{
      +  "maximum": 100000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. Changed6 schema fields changedv1.3.3
    • addedOutput schema / properties / error / properties / capacityAction
      Added value: +{
      +  "enum": [
      +    "review_plans",
      +    "contact_support"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / error / properties / getKeyUrl
      Added value: +{
      +  "maxLength": 256,
      +  "pattern": "^https:\\/\\/thepulse\\.markets\\/developers(?:[/?#][^\\s]*)?$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / error / properties / hostedServerUrl
      Added value: +{
      +  "const": "https://mcp.thepulse.markets/api/index/mcp",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / nextAction / enum
      Previous value: -[
      -  "wait",
      -  "review_access",
      -  "check_limits",
      -  "reconnect",
      -  "check_input",
      -  "choose_another_symbol",
      -  "report_issue"
      -]New value: +[
      +  "wait",
      +  "review_access",
      +  "check_limits",
      +  "reconnect",
      +  "check_input",
      +  "choose_another_symbol",
      +  "report_issue",
      +  "get_key"
      +]
    • addedOutput schema / properties / error / properties / resetAt
      Added value: +{
      +  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])T([01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d\\.\\d{3}Z$",
      +  "type": "string"
      +}
    • addedOutput schema / properties / error / properties / upgradeUrl
      Added value: +{
      +  "const": "https://thepulse.markets/developers#/portal/pricing",
      +  "type": "string"
      +}
  4. Addedv1.3.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark this as a non-destructive, idempotent, open-world write, and the description goes well beyond them by disclosing that the report is stored privately, that it has no trading or pricing side effects, and that the receipt is returned only after storage succeeds. The authentication requirement and the data-handling prohibition are behavioral facts the annotations cannot express.

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?

Five tight sentences with the purpose front-loaded, then prerequisites, then content restrictions, then side-effect scope, then return behavior. Every sentence carries information, though the negative clause about prices, trades and PRs is slightly padded relative to its value.

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 an eight-parameter mutation tool with an output schema, the definition covers purpose, auth, privacy constraints, side-effect boundaries and receipt timing, which is nearly everything an agent needs. It omits duplicate-submission behavior despite idempotentHint=true, and says nothing about failure modes when storage does not succeed.

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 description coverage is 100%, so all eight parameters are already documented, including the enums for category and surface and the reproduction line limits. The description adds only one piece of guidance beyond the schema, telling the agent to attach the failed call's requestId when available; the baseline 3 applies given how much the schema carries.

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 ('submit') and a specific resource (a reproducible Verity API or MCP bug / missing-capability / data-quality report) plus the destination ('for human review'). That immediately separates it from every sibling, all of which are read-only data-retrieval tools.

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?

Gives clear preconditions for use: a developer key (PULSE_API_KEY) or the hosted server, and an enabled feedback service, plus 'include the failed call's requestId when available.' It also sets a content boundary ('Do not send secrets, personal information or conversation transcripts') that tells the agent when not to use it. It does not name an alternative route for users who lack credentials, which keeps it short of a 5.

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