Skip to main content
Glama

YouSpot

by com.youspot
OverviewDiscussionsAdmin

Enrich brain object

enrich_graph_object

Fill the empty fields of one company, contact or web link in the user's graph from public data, the same as the Enrich button on its page. A company is looked up by its website, a contact by its LinkedIn profile or email, and a web link is read again for its summary, topics and key facts. Only empty fields are filled; nothing the user wrote is replaced, so it needs no approval. Returns which fields it filled. Use it when the user asks to enrich, fill in or flesh out a specific record. A company with no website can take one in 'domain'. For several records at once, pass up to 200 ids in 'object_ids': cached data fills at once and the rest is looked up in the background, so tell the user the records fill in over the next few minutes. There is a daily limit, so do not run it across the whole graph unasked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoThe company's website, only for a company that has none yet (e.g. 'saronic.com').
object_idNoThe company, contact or web link to enrich (exact id).
object_idsNoSeveral records to enrich at once, in place of object_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / object_ids
      Added value: +{
+  "description": "Several records to enrich at once, in place of object_id.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 200,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "object_id"
-]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the sole readOnlyHint=false annotation: it discloses that only empty fields are touched, nothing user-written is replaced, no approval is needed, the filled-fields result is returned, and batch calls fill cached data immediately while the rest is processed in the background over minutes. It also flags the daily rate limit.

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?

Purpose and the fill-only semantics are front-loaded, and the sentences are information-dense. It runs long (batch behavior, limits, per-type lookup rules), but almost every sentence earns its place, with only mild redundancy.

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?

For a mutation tool with no output schema, it covers the return ('which fields it filled'), the async batch caveat, the daily limit, and per-record-type lookup requirements. An agent has everything needed to call it correctly and set user expectations.

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% so the baseline is 3, but the description adds real meaning: 'domain' is only for a company that has no website, and 'object_ids' is the batch alternative to 'object_id' with a 200 cap and deferred background filling. This is more than the schema restates.

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?

States a specific verb (fill/enrich) and resource (company, contact or web link in the user's graph), and explicitly anchors it to the known 'Enrich button' behavior. It distinguishes itself from siblings like create_graph_object and set_graph_object_fields by clarifying it only fills empty fields and never overwrites user data.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions ('when the user asks to enrich, fill in or flesh out a specific record'), explains the batch path (up to 200 ids in object_ids versus single object_id), and states a when-not guardrail ('do not run it across the whole graph unasked' because of the daily limit).

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

All YouSpot toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources