Skip to main content
Glama
Sign In
servicenow-api

servicenow-api

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get hr profile

servicenow_get_hr_profile
Read-onlyIdempotent

Retrieve an HR profile from ServiceNow by user or sys_id, enabling HR data lookup for employee records and profile details.

Instructions

Invoke the get_hr_profile operation.

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": "servicenow_get_hr_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
sys_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds no behavioral context such as auth requirements, what an HR profile contains, or what happens when both identifiers are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence, which is technically concise, but the brevity stems from under-specification rather than from disciplined editing. The one sentence it does contain carries no informational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a lookup tool with no output schema, two undocumented identifier parameters, and no required parameters, the description should explain identity resolution and return shape. It explains neither, leaving the agent unable to determine how to form a valid call.

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

Parameters1/5

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

Schema description coverage is 0% for both parameters, and the description supplies no meaning for 'user' versus 'sys_id' or how they interact. With two undocumented, optional, mutually ambiguous identifier parameters, the description fails to compensate for the schema gap.

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

Purpose2/5

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

The description 'Invoke the get_hr_profile operation' is a tautology that restates the tool name and title without adding a verb-object statement of what is actually retrieved or from where. An agent learns nothing beyond what the name already encodes, and nothing distinguishes it from the roughly 100 sibling tools.

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 guidance on when to call this tool, when not to, or which alternatives exist (e.g. generic table/record readers like servicenow_get_table_record). The agent is given no selection criteria at all.

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

Deploy Server

Other Tools