Skip to main content
Glama

mcp-knowledge

by io.github.getgapup

term_sheet_negotiation

Read-only

Négociation term sheet — Gapup agent-payable C-suite expertise (FUNDRAISING). Returns a structured, audited deliverable. Reference case: Agicap Série C €50M — 8 clauses analysées · 3 rouges · Score fondateur 62/100 → plan pour 81. Inputs are validated server-side — send the documented case fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asyncNoIf true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client timeouts.
roundYes
companyYes
termSheetClausesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • addedInput schema / properties / company / properties
      Added value: +{
+  "name": {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  "sector": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / company / required
      Added value: +[
+  "name",
+  "sector"
+]
    • addedInput schema / properties / round / properties
      Added value: +{
+  "amountMEur": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "leadInvestor": {
+    "maxLength": 100,
+    "minLength": 2,
+    "type": "string"
+  },
+  "preMoneyValuation": {
+    "minimum": 0,
+    "type": "number"
+  },
+  "stage": {
+    "maxLength": 50,
+    "minLength": 2,
+    "type": "string"
+  }
+}
    • addedInput schema / properties / round / required
      Added value: +[
+  "stage",
+  "amountMEur",
+  "leadInvestor"
+]
    • addedInput schema / properties / termSheetClauses / items
      Added value: +{
+  "properties": {
+    "clause": {
+      "maxLength": 100,
+      "minLength": 2,
+      "type": "string"
+    },
+    "currentText": {
+      "maxLength": 500,
+      "minLength": 5,
+      "type": "string"
+    }
+  },
+  "required": [
+    "clause",
+    "currentText"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / termSheetClauses / maxItems
      Added value: +15
    • addedInput schema / properties / termSheetClauses / minItems
      Added value: +3
    • addedInput schema / required
      Added value: +[
+  "company",
+  "round",
+  "termSheetClauses"
+]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

The description states the tool returns a deliverable and validates inputs server-side, adding some context beyond the readOnlyHint annotation. However, it lacks details on performance, side effects, or failure modes.

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 description is relatively short and front-loaded with the purpose. The reference case adds some useful context but could be considered unnecessary fluff. Overall, it is concise but not minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complex nested input schema and no output schema, the description is incomplete. It does not describe the deliverable format, scoring interpretation, or what the output looks like, leaving the agent with significant gaps.

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?

The schema has low description coverage (25%) with only the async parameter documented. The description does not explain the meaning of company, round, or termSheetClauses, nor their nested fields. It only says 'send the documented case fields,' which is insufficient.

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 clearly states the tool performs term sheet negotiation analysis and returns a structured deliverable, with a specific reference case. However, it does not distinguish this from sibling tools like deal_coach or cap_table_strategist, which could be similar.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description only mentions 'Gapup agent-payable C-suite expertise' and a reference case, but no explicit when-to-use or when-not-to-use context.

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

All mcp-knowledge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.8/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially in competitive intelligence, ESG, and risk assessment. For example, there are multiple tools for competitor analysis (competitive_deep_dive, competitor_intel, competitor_moves, etc.) with unclear boundaries. Agents would struggle to select the correct tool without deep understanding of subtle differences.

Naming Consistency2/5

Tool names are a mix of English and French, and follow no consistent pattern. Some use snake_case (e.g., abm_architect, action_plan_esg), while others are verb-focused (e.g., content_catalog, fx_rate). The lack of a uniform naming convention makes it hard for agents to predict tool names.

Tool Count1/5

With 271 tools, the server is excessively large. Even for a broad knowledge domain, this number of tools makes discovery and selection inefficient. Typical coherent servers have 3-15 tools; this has an order of magnitude more, indicating poor scoping.

Completeness3/5

The tool set covers many domains (compliance, finance, marketing, HR, etc.), but the coverage is uneven due to redundancy. Key areas have multiple overlapping tools, while some sub-domains may still have gaps. Overall, the surface is broad but not well-curated.

Resources