Skip to main content
Glama
Sign In
brief-mcp

brief-mcp

by MLDreamer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Crm Context

get_crm_context

Look up a person in HubSpot CRM to retrieve deal stage, last contact date, lifecycle stage, associated deals, and interaction notes for meeting prep.

Instructions

Look up a person in HubSpot CRM.

Returns deal stage, last contact date, lifecycle stage, associated deals, and interaction notes for the given person.

Set HUBSPOT_API_KEY in .env to enable CRM integration.

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

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person to look up (required).
emailNoEmail address for a more precise match (optional but recommended).
companyNoCompany name to narrow the search (optional).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral context by listing the returned fields and disclosing the HUBSPOT_API_KEY/.env configuration requirement, which tells the agent the integration may be disabled. It still omits what happens when the key is missing, whether the call is read-only, and any rate or lookup-miss behavior.

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?

Three short, front-loaded blocks: the action first, then the payload, then the setup caveat. No filler sentences, though the setup note could have been folded into the first line for even tighter structure.

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 the description is not obligated to explain return values, and it still summarizes them usefully. The auth prerequisite is surfaced, leaving only sibling-routing guidance as a meaningful gap.

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% and each parameter is documented in the schema, so the baseline is 3. The description adds no parameter-level detail (matching semantics, whether name alone is sufficient, how company narrows results) beyond what the schema already states.

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 ('Look up a person in HubSpot CRM') and enumerates the returned data fields, which makes the tool's scope unambiguous. It does not, however, distinguish itself from the sibling 'enrich_brief_with_crm' or 'get_person_history', which an agent could reasonably confuse it with.

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?

The description never says when to reach for this tool versus the many adjacent siblings (enrich_brief_with_crm, get_person_history, research_attendee). No prerequisites, triggers, or exclusions are given beyond the setup note.

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