Skip to main content
Glama

SourceGeek

Get employee profile with recommendations

employee_profile_with_recommendations
Read-only

Fetch a person's full public profile together with received and given recommendations in one call (2 credits).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "usernameOrUrl": "<usernameOrUrl>"
    },
    "name": "employee_profile_with_recommendations"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful non-schema behavior: the call costs 2 credits and bundles two result sets. It does not say how 'limit' interacts with the two bundled result sets, nor how large a profile typically is.

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?

A single sentence, front-loaded with the verb and the composite payload, with the cost appended at the end where it belongs. Nothing is wasted and nothing is buried.

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?

For a 2-parameter, no-output-schema tool this covers the basics, and annotations carry the safety profile. The notable gap is the ambiguity of how 'limit' maps onto the bundled profile-plus-two-recommendation-sets result, which an agent needs in order to size the call correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented, including the 1-100 range and the username/URL forms. The description adds nothing about whether 'limit' applies to recommendations, profile sections, or both, so it sits at the baseline for fully documented schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Fetch'), a specific composite resource ('full public profile together with received and given recommendations') and a scope ('public'). The 'with recommendations' qualifier lets an agent distinguish it from sibling profile tools like employee_profile_full_with_posts or employee_profile_about, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this composite call over the many single-purpose profile siblings (about, posts, reactions, interests). The phrase 'in one call' hints at a batching rationale, but the agent must infer the trade-off rather than being told it.

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.

Resources