Skip to main content
Glama

SourceGeek

Get a person's last activity

employee_profile_recent_activity_time
Read-only

Return when a person was last active (timestamp, relative age such as '1d', and activity type).

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_recent_activity_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered without description help. The description does add the return shape (timestamp, relative age, activity type), which matters because there is no output schema, but it says nothing about how activity is scoped, whether missing profiles error or return empty, or how fresh the data is.

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?

One front-loaded sentence with the primary outcome first and the return components in a tight parenthetical. Nothing is wasted, though it is minimal enough that a little more routing detail would fit without bloat.

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 one-parameter read tool, the description plus annotations covers what the agent needs to call it, and the return fields are described even without an output schema. The main remaining gap is behavior on unresolvable or private profiles.

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 coverage is 100% and the single parameter's description already explains the accepted username and URL formats. The description adds no meaning beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource: return when a person was last active, with the three components of the answer named. It is clearly distinct from siblings like employee_profile_posts or employee_profile_about, though it never explicitly contrasts itself with them.

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 when-to-use guidance, no conditions, and no mention of alternatives such as employee_profile_posts when the agent actually needs activity content rather than recency. Usage is only inferable from the narrow name.

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