Skip to main content
Glama

Equitest

Save an Insights M&A report draft (admin)

save_ma_insight
Idempotent

Admin only. Saves (creates or updates) the DRAFT of an Equitest Insights M&A report for one period. The numbers, charts and tables on the page are recomputed on the server from the database — only the text is taken from here. Nothing goes live: the admin opens the returned preview_url on equitest.net and clicks Publish. A published report cannot be changed here — unpublish it on the site first. Follow the writing guide returned by ma_period_digest.

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": {
      "period_type": "<period_type>",
      "period": "<period>",
      "title": "<title>",
      "body_html": "<body_html>"
    },
    "name": "save_ma_insight"
  }
}

Input Schema

NameRequiredDescriptionDefault
dekNoOne-sentence standfirst under the title, up to 160 characters
faqNo4–6 questions and answers shown as an FAQ section with FAQPage structured data
titleYesPage title, e.g. "Global M&A Report — Q3 2026: Industrial Buyers Lead"
periodYesMonth "2026-09", quarter "2026-Q3" or year "2026"
summaryNoMeta description for search engines, up to 155 characters
body_htmlYesThe analysis: <h2>, <p>, <ul>/<li>, <strong>, <em>, <blockquote>, <table>. Sanitised on save.
highlightsNo3–5 key takeaways, each built around one figure
period_typeYesReport period type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / faq
      Added value: +{
      +  "description": "4–6 questions and answers shown as an FAQ section with FAQPage structured data",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "a": {
      +        "description": "Answer, 1–3 sentences, plain text",
      +        "type": "string"
      +      },
      +      "q": {
      +        "description": "Question",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "q",
      +      "a"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 8,
      +  "type": "array"
      +}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the mechanical profile (not read-only, idempotent, non-destructive, closed-world); the description adds the semantics an agent actually needs: only text is taken, numbers/charts/tables are recomputed server-side, nothing goes live on save, and the returned preview_url must be published manually. It also discloses the failure mode for published periods, which no annotation conveys.

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

Conciseness5/5

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

Five short sentences, front-loaded with the access constraint and the draft scope, then the recompute rule, then the publish gate, then the writing-guide pointer. No sentence is redundant with the title or schema.

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?

For an 8-parameter mutation tool with no output schema, the description covers access control, side effects, lifecycle after save, an explicit return value (preview_url), and where to get authoring guidance. Nothing an agent needs to call this correctly and follow up is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying that numeric/chart content must not be supplied and only text fields matter, which steers how body_html and the array parameters should be filled. It does not, however, explain the coupling between period_type and the period string format, leaving that to the schema.

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 and resource ("Saves (creates or updates) the DRAFT of an Equitest Insights M&A report"), scopes it to one period, and explicitly distinguishes the draft from the live published artifact. An agent can immediately tell this is the write path for report text, distinct from read-only siblings like list_ma_insights or ma_period_digest.

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?

Gives an explicit precondition ("Admin only"), an explicit when-not ("A published report cannot be changed here — unpublish it on the site first"), and routes the agent to the sibling ma_period_digest for the required writing guide. The post-save workflow (open preview_url on equitest.net and click Publish) is spelled out so the agent knows saving is not the final step.

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