Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

get_vc

Read-only

UNDERSTANDING — One VC firm: identity, fund facts, and portfolio summary (totals, band distribution, average rating). Pass view=full to inline the whole portfolio. Understanding plan. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
slugYesVC firm slug, lowercase and hyphenated, as find_vcs returns it.
viewNosummary (default, lean) or full.summary
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
    • changedInput schema / properties / view / description
      Previous value: -"summary (default) returns lean discovery records + *_count for dropped sections; full returns the whole record (use get_api / get_provider for one entity)."New value: +"summary (default, lean) or full."
  2. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"VC firm slug, lowercase and hyphenated, as find_vcs returns it."
  3. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  4. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: the $0.01-per-call pricing under pay-as-you-go, inclusion in specific plans, and the pointer to apis://prices for current rates. This discloses cost/auth-plan implications the agent would not otherwise know.

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-loads the core noun phrase (one VC firm + what's returned) before moving to the view option and pricing. It is dense but each clause carries information; the price/plan sentence is slightly tangential but relevant to invocation decisions.

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 usefully enumerates what is returned (identity, fund facts, totals, band distribution, average rating) and covers all three parameters plus the view toggle. Missing only explicit sibling routing, which keeps it from a 5.

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 slug, view (with enum), and context are all documented in the schema itself. The description echoes view=full inline behavior but adds no syntax or semantics beyond the enum/default already present. Baseline 3 is appropriate.

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?

States a specific verb and resource — retrieving a single VC firm's identity, fund facts, and portfolio summary — and distinguishes it implicitly from find_vcs (plural search) and vc_portfolio. It does not explicitly name the sibling tools, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description tells the agent to pass view=full to inline the whole portfolio, which is a useful usage hint, and it clarifies pricing/plan eligibility (Understanding, Influence, pay-as-you-go). However, it never says when NOT to use this tool or points to find_vcs for discovery, so routing guidance is only implied.

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

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources