Skip to main content
Glama

BTCDecoded Intelligence

analyze_submission

Read-onlyIdempotent

Advisory spec-versus-submission check. Retrieves cited index passages, then a closed judge label: met, not_met, or ambiguous. Empty or off-topic cite packs are ambiguous. Scores a named requirement only when a packed cite bears on it. structuredContent.rationale names met, unmet, and unaddressed requirements without pasting excerpts. Optional public GitHub PR (github_pr) is packed; private repos fail. Not a merge, payout, or money check. Does not post comments.

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": {
      "spec": "<spec>",
      "submission": "<submission>"
    },
    "name": "analyze_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYesNatural-language spec or acceptance criteria to check against.
whenNoOptional date pin YYYY, YYYY-MM, or YYYY-MM-DD. Keeps cites whose passage date starts with that prefix.
sourceNoOptional pin to one corpus source (e.g. github, irc, mail, spec). Omit to search both layers.
github_prNoOptional public GitHub PR URL (https://github.com/owner/repo/pull/n) or ref (owner/repo#n). Packed into the submission. Private repos fail. Not an arbitrary URL fetch.
caller_refNoOptional opaque correlation id. Echoed, not interpreted.
submissionYesNatural-language submission text (description and/or public PR pack).
requirementsNoOptional named criteria strings. When present, the judge scores a criterion 0-1 only if packed cites bear on it; otherwise the score is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "stackexchange",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts",
      -  "project"
      -]New value: +[
      +  "corpus",
      +  "legal",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "repo-analysis",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "stackexchange",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts",
      -  "project"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "stackexchange",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price",
      -  "transcripts"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts",
      +  "project"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "slips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price",
      +  "transcripts"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "sv2",
      -  "ln-spec",
      -  "tooling",
      -  "hw",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "slips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / requirements / description
      Previous value: -"Optional named criteria strings. When present, the judge may score each 0-1 from the cite pack."New value: +"Optional named criteria strings. When present, the judge scores a criterion 0-1 only if packed cites bear on it; otherwise the score is omitted."
  7. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "corpus",
      -  "findings",
      -  "spec",
      -  "book",
      -  "maintainers",
      -  "secsov",
      -  "commons-whitepaper",
      -  "bitcoin-whitepaper",
      -  "articles",
      -  "papers",
      -  "textbooks",
      -  "nips",
      -  "sv2",
      -  "ln-spec",
      -  "synthesis",
      -  "blvm-docs",
      -  "pool",
      -  "vision",
      -  "governance",
      -  "github",
      -  "irc",
      -  "mail",
      -  "delving",
      -  "bitcointalk",
      -  "core_src",
      -  "src",
      -  "satoshi",
      -  "releases",
      -  "bips",
      -  "price"
      -]New value: +[
      +  "corpus",
      +  "findings",
      +  "spec",
      +  "book",
      +  "maintainers",
      +  "secsov",
      +  "commons-whitepaper",
      +  "bitcoin-whitepaper",
      +  "articles",
      +  "papers",
      +  "textbooks",
      +  "nips",
      +  "sv2",
      +  "ln-spec",
      +  "tooling",
      +  "hw",
      +  "synthesis",
      +  "blvm-docs",
      +  "pool",
      +  "vision",
      +  "governance",
      +  "github",
      +  "irc",
      +  "mail",
      +  "delving",
      +  "bitcointalk",
      +  "core_src",
      +  "src",
      +  "satoshi",
      +  "releases",
      +  "bips",
      +  "price"
      +]
  8. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, and the description still adds substantive context: the two-stage retrieve-then-judge flow, the closed label set, how empty/off-topic cite packs resolve, that the rationale names met/unmet/unaddressed requirements without pasting excerpts, and that private repos fail. This is behavior beyond what the structured fields convey.

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 core purpose and negative boundaries are front-loaded in the first sentences, and each sentence carries information (label set, cite-pack rules, PR handling, exclusions). The telegraphic phrasing ("Not a merge, payout, or money check") is dense but occasionally clipped enough to read as fragments rather than fully structured prose.

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?

With no output schema, the description does the work of explaining the return shape — the closed label plus a structuredContent.rationale enumerating met, unmet, and unaddressed requirements. Combined with the failure mode for private repos and the no-side-effect guarantees, an agent has enough to call it correctly, with only minor gaps around output field names.

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 100%, so each of the seven parameters is already documented in the schema, including the date-prefix semantics of 'when' and the PR-URL format of 'github_pr'. The description reinforces that requirements are only scored when cites bear on them, but adds little syntactic or format meaning beyond the schema, so baseline 3 applies.

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 states a specific verb and resource ("spec-versus-submission check") and names the output form (a closed judge label of met, not_met, or ambiguous). It also draws negative boundaries ("Not a merge, payout, or money check"), though it never names a sibling tool such as verify_claim or analyze_pr, so differentiation from the catalog is implied rather than explicit.

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 gives clear when-to-use conditions and edge-case rules: empty or off-topic cite packs are ambiguous, a named requirement is only scored when a packed cite bears on it, and private-repo PRs fail. Exclusions are stated (not a merge/payout/money check, does not post comments), but there is no explicit routing to an alternative tool when this one is the wrong choice.

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