Anchord MCP

ingest_record

Ingest a record from any registered source system and automatically match it to a canonical AnchorID.

Instructions

Ingest a single source record into Anchord. The record is matched to an AnchorID automatically. Requires a registered source (system). Wraps POST /ingest/batch with a single-item array.

Input Schema

TableJSON Schema

Name	Required	Description
`system`	Yes	Source system key (e.g. hubspot, salesforce, stripe, or a custom source)
`object_type`	Yes	Object type within the source (e.g. company, contact, customer)
`object_id`	Yes	Unique ID of the record in the source system
`payload`	Yes	Record payload — key/value fields (e.g. name, domain, email)

Implementation Reference

src/tools.ts:355-356 (registration)
Tool registration of 'ingest_record' on the MCP server via server.tool()
```
server.tool(
  "ingest_record",
```

src/tools.ts:360-367 (schema)

Input schema for ingest_record using Zod: requires system, object_type, object_id, and payload fields

{
  system: z.string().describe("Source system key (e.g. hubspot, salesforce, stripe, or a custom source)"),
  object_type: z.string().describe("Object type within the source (e.g. company, contact, customer)"),
  object_id: z.string().describe("Unique ID of the record in the source system"),
  payload: z
    .record(z.unknown())
    .describe("Record payload — key/value fields (e.g. name, domain, email)"),
},

src/tools.ts:368-377 (handler)

Handler that POSTs the input wrapped in a records array to /ingest/batch, using the ApiClient

async (input) => {
  try {
    const data = await api.post("/ingest/batch", {
      records: [input],
    });
    return jsonContent(data);
  } catch (e) {
    return errorContent(e);
  }
},

src/tools.ts:354-354 (helper)

Comment header for the 10th tool: ingest_record

// ─── 10. ingest_record ──────────────────────────────────────────

src/tools.ts:357-359 (helper)

Description string explaining the tool wraps POST /ingest/batch with a single-item array

"Ingest a single source record into Anchord. The record is matched to an " +
  "AnchorID automatically. Requires a registered source (system). " +
  "Wraps POST /ingest/batch with a single-item array.",

Tool Definition Quality

A3.9/5.0

Behavior3/5

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

No annotations provided, so the description must carry full burden. It discloses that it is a write operation, requires a registered source, automatically matches to AnchorID, and wraps a batch endpoint. However, it lacks details on idempotency, error handling, or response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the primary action, and every statement contributes to understanding without redundancy.

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

Completeness3/5

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

The description covers the core operation and prerequisite but omits return value details (e.g., the resulting AnchorID). Given no output schema, this information would be valuable for an agent.

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%, but the description adds value by explaining that the system must be registered and that payload is sent as a single-item array to a batch endpoint, which clarifies usage beyond the schema descriptions.

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 uses specific verbs and resources: 'Ingest a single source record into Anchord', clearly stating the action and target. It distinguishes from siblings by explaining the automatic AnchorID matching and requirement for a registered source.

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 mentions a prerequisite (requires a registered source) but does not explicitly compare to sibling tools like guard_write or guard_write_batch. The usage context is implied but not fully delineated.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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/nolenation04/anchord-mcp'

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