Skip to main content
Glama
Sign In
Andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Brief on portfolio go-to-market

generate_portfolio_brief

Generate a written brief on up to 15 portfolio companies' go-to-market activity for a chosen period, covering targets, public news, buyer market signals, and sources.

Instructions

Portfolio oversight: use this when a PE or VC operator wants a written brief on their portfolio companies' go-to-market activity for a period: what Andru's work across the companies found (targets, opportunities, overlaps), each company's public go-to-market news, and the market signals around their buyers, with sources. Not a financial or performance report. Send the companies (name and website, up to 15) or a portfolioId; with neither, Andru suggests the companies on the firm's website for the person to confirm. Takes a few minutes: returns a job_id; call get_asset with it. Paid. Check the price with quote before running.

Input Schema

NameRequiredDescriptionDefault
quoteIdNoOptional: the quote_id from quote, to pay the quoted price (held for 30 minutes).
companiesNoThe portfolio companies to brief, up to 15. Saved as a portfolio on your account the first time.
periodEndNoOptional ISO date for the period end. Default: the end of the last full period.
periodTypeNoReporting period type. Default quarterly.
periodStartNoOptional ISO date for the period start. Default: the start of the last full period.
portfolioIdNoA portfolio already on your account (returned by an earlier brief). With companies, they are added to it.
idempotencyKeyNoOptional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.
maxAmountCentsNoOptional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.4.9
    • addedInput schema / properties / idempotencyKey
      Added value: +{
+  "description": "Optional: any unique string for this call. Retrying with the same key returns the first result and never charges twice.",
+  "type": "string"
+}
    • addedInput schema / properties / maxAmountCents
      Added value: +{
+  "description": "Optional: the most this call may cost, in cents. If the price is higher, nothing runs and nothing is charged.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / quoteId
      Added value: +{
+  "description": "Optional: the quote_id from quote, to pay the quoted price (held for 30 minutes).",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.4.8
    • addedInput schema / properties / companies
      Added value: +{
+  "description": "The portfolio companies to brief, up to 15. Saved as a portfolio on your account the first time.",
+  "items": {
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "website": {
+        "description": "e.g. example.com; tells companies with similar names apart.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "maxItems": 15,
+  "type": "array"
+}
    • changedInput schema / properties / portfolioId / description
      Previous value: -"The portfolio to brief. Must belong to the caller."New value: +"A portfolio already on your account (returned by an earlier brief). With companies, they are added to it."
    • removedInput schema / required
      Removed value: -[
-  "portfolioId"
-]
  3. Changed2 schema fields changedv1.4.4
    • changedInput schema / properties / periodEnd / description
      Previous value: -"Optional ISO date for the period end."New value: +"Optional ISO date for the period end. Default: the end of the last full period."
    • changedInput schema / properties / periodStart / description
      Previous value: -"Optional ISO date for the period start."New value: +"Optional ISO date for the period start. Default: the start of the last full period."
  4. Addedv1.4.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description adds what the agent actually needs: the call is slow ("takes a few minutes"), returns a job_id rather than the brief, is paid, and the price must be quoted first. That async + billing behavior is invisible from annotations or schema.

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?

Front-loaded with the oversight use case and tightly packed with distinct information — no filler sentences. The first sentence is long and clause-heavy ("for a period: what Andru's work across the companies found..."), which slightly slows parsing, but nothing is redundant.

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 async, paid, zero-required-parameter tool with no output schema, the description covers the full lifecycle: inputs or fallback, latency expectation, job_id return, retrieval via get_asset, and price control via quote. An agent can invoke and follow through correctly without further information.

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 baseline is 3; the description adds meaning by explaining the companies/portfolioId interaction and the no-input fallback where Andru proposes companies from the firm's website for confirmation. It doesn't add format guidance for periodStart/periodEnd or the quoteId/maxAmountCents linkage beyond what the schema already states.

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+resource (written brief on portfolio companies' go-to-market activity) and enumerates the contents: targets/opportunities/overlaps, public GTM news, market signals, with sources. It also draws an explicit negative boundary ("Not a financial or performance report"), which separates it from get_portfolio_readiness_rollup and financial siblings.

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?

Names the actor and situation precisely ("when a PE or VC operator wants..."), specifies the required input paths (companies or portfolioId) and the fallback when neither is supplied. It also routes to sibling tools explicitly: quote before running, get_asset to retrieve the result.

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

Deploy Server

Other Tools