Skip to main content
Glama

sn_profile

Read-onlyIdempotent

Inspect non-secret metadata and the effective policy card for a selected ServiceNow profile, including tables, tools, fields, and batch limits, without changing configuration or exposing credentials.

Instructions

Inspect non-secret metadata and the effective policy card (tables, tools, fields, batch limits) for an explicitly selected ServiceNow profile. Profiles are created, modified, and selected out of band by the operator; this tool never changes profile configuration or reveals credentials.

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": {
      "profile": "<profile>"
    },
    "name": "sn_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesConfigured ServiceNow profile name (required; no default fallback).

Output Schema

NameRequiredDescriptionDefault
dataYes
profileYesConfigured ServiceNow profile name (required; no default fallback).
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety bar is lower; the description still adds real value by asserting it never mutates profile configuration and never reveals credentials, and by clarifying that profiles are managed out of band. It stops short of covering failure behavior for an unknown or unconfigured profile name.

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?

Two sentences, front-loaded with the core action and its scope, followed by the safety boundary. The parenthetical inventory is dense but informative; there is no redundant phrasing.

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?

An output schema exists, so return values need not be spelled out, and the description still summarizes the payload at a high level. For a single-parameter read-only tool with rich annotations, the remaining gaps (error cases, profile-name examples) are minor.

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 profile parameter is fully documented in the schema, including the no-default-fallback rule. The description reinforces that the profile must be explicitly selected but adds no syntax or naming conventions beyond what the schema already provides, so the baseline of 3 applies.

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 (Inspect) and a specific resource (non-secret metadata and the effective policy card for a ServiceNow profile), and enumerates what the card covers (tables, tools, fields, batch limits). It is clear what the tool does, but it never names or contrasts a sibling such as sn_health or sn_schema, so the agent must infer the boundary itself.

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

Usage Guidelines3/5

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

Usage is only implied: 'for an explicitly selected profile' and 'profiles are created, modified, and selected out of band by the operator' tell the agent prerequisites, but there is no explicit statement of when to choose this over sn_health, sn_schema, or sn_discover. Adequate context, no routing guidance.

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