Skip to main content
Glama

Base MPP Session-Metered Multi-Source Research Dossier Compiler

compile_mpp_research_dossier
Read-onlyIdempotent

Compiles a structured JSON research dossier ('key_findings', 'synthesis_quality_score', 'sources_cited') settled via Base EVM Machine Payments Protocol (MPP). Use when generating a strict-JSON cited intelligence brief paid via Base USDC MPP session headers; for running long-form narrative research reports via L402 Lightning, use conduct_deep_research_investigation instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'research_topic' ('output_density' defaults to 'concise_5_points'), supports '?demo=true' or MPP (300 sats), and returns HTTP 400 if invalid.

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": {
      "query": "<query>"
    },
    "name": "compile_mpp_research_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesResearch topic or technical question to investigate and structure into JSON.
output_densityNoGranularity of the key_findings array; defaults to 'executive_10_points' when omitted.
research_topicNoAlias for query: research topic or technical question to investigate.

Output Schema

NameRequiredDescriptionDefault
queryYesInvestigated research query.
key_findingsYesHigh-density factual bullet strings synthesized from live sources.
sources_citedYesVerified grounding source references.
synthesis_quality_scoreYesSelf-audit completeness score from 90 to 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / research_topic
      Added value: +{
      +  "description": "Alias for query: research topic or technical question to investigate.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "research_topic"
      -]New value: +[
      +  "query"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "search_prompt",
      -  "key_findings",
      -  "synthesis_quality_score",
      -  "sources_cited"
      -]New value: +[
      +  "query",
      +  "key_findings",
      +  "synthesis_quality_score",
      +  "sources_cited"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / required
      Previous value: -[
      -  "query"
      -]New value: +[
      +  "research_topic"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "query",
      -  "key_findings",
      -  "synthesis_quality_score",
      -  "sources_cited"
      -]New value: +[
      +  "search_prompt",
      +  "key_findings",
      +  "synthesis_quality_score",
      +  "sources_cited"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, yet the description adds genuinely new operational facts: stateless edge call, 32 KB response cap, 60 RPM limit, 300 sats MPP pricing, '?demo=true' bypass, and HTTP 400 on invalid input. That is exactly the beyond-annotation context the dimension rewards.

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?

Two tightly packed sentences that front-load purpose, then routing, then operational limits. Nothing is truly wasted, but the run-on density (pricing, rate limit, size cap, error code in one breath) makes it slightly harder to scan than necessary.

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?

An output schema exists, so return values needn't be explained, and the description still covers cost, limits, error behavior and the alternative tool. The one material gap is the mismatched parameter naming and default value, which leaves an agent unsure whether to send 'query' or 'research_topic' and what default applies.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description introduces conflicting facts: it says 'output_density' defaults to 'concise_5_points' while the schema says 'executive_10_points', and it presents 'research_topic' as an accepted input while the schema's required field is 'query'. Those mismatches actively mislead rather than add meaning.

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?

A specific verb ("Compiles") plus a well-defined resource ("structured JSON research dossier") with the returned fields named inline ('key_findings', 'synthesis_quality_score', 'sources_cited'). It also names the sibling it is not (conduct_deep_research_investigation for L402 narrative reports), so an agent can separate the two without opening either schema.

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?

Explicit when-to-use ("generating a strict-JSON cited intelligence brief paid via Base USDC MPP session headers") paired with an explicit alternative and the condition selecting it (L402 long-form narrative → conduct_deep_research_investigation). Payment mode and demo-mode fallback are also stated, leaving little to inference.

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.