Skip to main content
Glama

Guide: ID guide

agent_id_guide
Read-onlyIdempotent

Return the authoritative Nilyo ID semantics guide. Use this when unsure whether a tool needs a LinkedIn system user ID, public identifier, request ID, post/comment/chat/message ID, inbox/contract ID, email/thread/folder/attachment ID, calendar/event ID or recruiting/list ID. The guide explains exactly which previous tool produces each ID and which lookalike values must NOT be passed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agent_id_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id_type / enum
      Previous value: -[
      -  "linkedin_user_id",
      -  "linkedin_public_identifier",
      -  "linkedin_company_id",
      -  "relation_request_id",
      -  "post_id",
      -  "comment_id",
      -  "chat_id",
      -  "message_id",
      -  "inbox_id",
      -  "contract_id",
      -  "job_id",
      -  "email_id",
      -  "email_reply_id",
      -  "thread_id",
      -  "folder_id",
      -  "attachment_id",
      -  "calendar_id",
      -  "event_id",
      -  "recruiter_project_id",
      -  "applicant_id",
      -  "sales_nav_list_id"
      -]New value: +[
      +  "facebook_ids",
      +  "linkedin_user_id",
      +  "linkedin_public_identifier",
      +  "linkedin_company_id",
      +  "linkedin_managed_company_id",
      +  "relation_request_id",
      +  "post_id",
      +  "comment_id",
      +  "chat_id",
      +  "message_id",
      +  "inbox_id",
      +  "contract_id",
      +  "job_id",
      +  "email_id",
      +  "email_reply_id",
      +  "thread_id",
      +  "folder_id",
      +  "attachment_id",
      +  "calendar_id",
      +  "event_id",
      +  "recruiter_project_id",
      +  "applicant_id",
      +  "sales_nav_list_id"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds real value beyond them: it is framed as the authoritative source, and it discloses that the guide maps each ID to the producing tool and flags lookalike values that must not be passed. Return shape is not described, but the content is characterized well.

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 action is front-loaded in the first sentence and the trigger condition follows immediately. The long trailing enumeration of ID types is dense but each item is load-bearing for matching user vocabulary; it could be tightened but is not wasteful.

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?

For a single read-only lookup tool with no output schema and no required params, the description conveys the subject matter and how the guide is meant to be used. The only gap is behavior when id_type is omitted versus supplied.

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 description coverage is 0%, so the description must carry the param, and it does by enumerating nearly every enum domain (user, public identifier, request, post/comment/chat/message, inbox/contract, email/thread/folder/attachment, calendar/event, recruiting/list). It does not clarify that id_type is optional or what omitting it returns.

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?

Specific verb+resource ('Return the authoritative Nilyo ID semantics guide') followed by an enumeration of the exact ID domains covered. An agent can tell it apart from the capability/messaging/resolve-style siblings without opening the schema.

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?

Gives an explicit trigger: 'Use this when unsure whether a tool needs a ... ID', which is exactly the decision point an agent hits before calling resolve/profile/message tools. It does not name a competing sibling (e.g. agent_capability_guide) or state when-not to use it, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.