Skip to main content
Glama
alludium

Affinity MCP Server

by alludium

Get Company

affinity_get_company
Read-onlyIdempotent

Retrieve a company's details by ID from Affinity CRM, optionally including enriched data (description, funding, employees) and custom fields.

Instructions

Get a single company by ID from Affinity CRM.

Returns company details with optional field data. Without fieldTypes/fieldIds, returns only basic info (id, name, domain, domains, isGlobal).

Field Types:

  • enriched: Data from Affinity Data and Dealroom (description, employees, funding, location, LinkedIn, etc.)

  • global: Your account's custom company fields

Returns (JSON): { "id": number, // Company ID "name": string, // Company name "domain": string, // Primary domain "domains": string[], // All domains "isGlobal": boolean, // Is shared record "fields": [ // Field data (if requested) { "id": string, // Field ID "type": string, // "enriched" or "global" "name": string, // Field name "value": { "type": string, // Value type "data": any // Field value } } ] }

Example field IDs you can request:

  • affinity-data-description

  • affinity-data-number-of-employees

  • affinity-data-location

  • affinity-data-total-funding-amount

  • affinity-data-linkedin-url

  • affinity-data-industry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany ID (numeric). Get IDs from affinity_list_companies or affinity_get_list_entries.
fieldTypesNoField categories to include. Options: "enriched" (Affinity Data, Dealroom), "global" (custom fields).
fieldIdsNoSpecific field IDs to return. Example: ["affinity-data-description", "affinity-data-location"]
responseFormatNoOutput format: "json" for structured data or "markdown" for human-readable. Default: "json"
Behavior5/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false. The description adds rich behavioral details: return structure, field categories (enriched vs global), and example field IDs. No contradictions.

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 well-structured with headings and bullet points. It is slightly lengthy due to the full return schema example, but every part is informative and earns its place.

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?

Despite lacking an output schema, the description provides a complete return JSON schema, covers optional parameters, and explains field types. It fully equips the agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description adds significant value: explains the interaction between fieldTypes and fieldIds, provides example field IDs, and clarifies the default behavior without these parameters.

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?

The description clearly states 'Get a single company by ID from Affinity CRM.' The verb 'get' and resource 'company' are specific. It distinguishes from sibling tools like affinity_list_companies (which lists all companies) and affinity_get_company_list_entries.

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

Usage Guidelines4/5

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

The description explains the effect of optional parameters (fieldTypes/fieldIds) on the response, guiding when to use them. It implies usage for fetching a single company by ID but lacks explicit when-not or alternative comparisons.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alludium/affinity-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server