Skip to main content
Glama

get_my_referrals

Track your referred candidates' recruitment status at Appinventiv, from referral date to current stage like Shortlisted or Hired.

Instructions

View all candidates you have referred to Appinventiv and their current recruitment pipeline status. Returns candidate name, position referred for, referral date, and status (e.g. Shortlisted, Rejected, Hired). Use get_job_openings() to find open positions you can refer people for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description must convey behavior. It implies a read-only operation ('View') and lists returned fields, but does not explicitly state side-effect-free or permission requirements. Adequate but not detailed.

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?

Three concise sentences: purpose, return details, and related tool. No wasted words, well-structured.

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?

Given zero parameters and an output schema, the description covers all necessary information: what it does, what it returns, and a pointer to a sibling tool. Fully adequate.

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?

No parameters, so baseline is 4. Description adds value by listing returned fields, which aids understanding of the output.

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 the verb 'View' and the resource 'candidates you have referred', with additional detail on pipeline status. It distinguishes from siblings as no other tool handles referrals.

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 provides context for when to use the tool (view your referrals) and explicitly mentions an alternative tool (get_job_openings) for finding open positions. It lacks explicit exclusions but offers clear guidance.

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/SookieAI/hrms-mcp'

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