Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

get_metadata_source

Fetches a single ServiceNow source record by name or sys_id for a specified source type, returning its body and a flag indicating whether the preview was truncated.

Instructions

Get one source record (SI/BR/widget) by name/sys_id. Returns body; 'complete' flags if truncated preview.

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": {
      "source_type": "<source_type>",
      "source_id": "<source_id>"
    },
    "name": "get_metadata_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_idYessys_id, name, or logical identifier
source_typeYesSpecific source type (not 'all').
max_field_lengthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.19
    • changedInput schema / properties / source_type / enum
      Previous value: -[
      -  "script_include",
      -  "widget",
      -  "angular_provider",
      -  "business_rule",
      -  "client_script",
      -  "catalog_client_script",
      -  "ui_action",
      -  "ui_script",
      -  "ui_page",
      -  "ui_macro",
      -  "scripted_rest",
      -  "fix_script",
      -  "scheduled_job",
      -  "script_action",
      -  "email_notification",
      -  "acl",
      -  "transform_script",
      -  "processor",
      -  "sp_header_footer",
      -  "sp_css",
      -  "ng_template",
      -  "update_xml"
      -]New value: +[
      +  "script_include",
      +  "widget",
      +  "angular_provider",
      +  "business_rule",
      +  "client_script",
      +  "catalog_client_script",
      +  "ui_action",
      +  "ui_script",
      +  "ui_page",
      +  "ui_macro",
      +  "ui_policy",
      +  "scripted_rest",
      +  "fix_script",
      +  "scheduled_job",
      +  "script_action",
      +  "email_notification",
      +  "acl",
      +  "transform_script",
      +  "processor",
      +  "sp_header_footer",
      +  "sp_css",
      +  "ng_template",
      +  "sp_theme",
      +  "sp_portal",
      +  "ux_theme",
      +  "ux_style",
      +  "update_xml"
      +]
  2. First observedv1.18.41

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behaviors: it returns the record body, and a 'complete' flag indicates whether the returned body was a truncated preview. It says nothing about permissions, not-found/error behavior, or what triggers truncation relative to max_field_length, so the disclosure is partial.

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 short, front-loaded sentences with no wasted wording, and the return/truncation note sits usefully at the end. The parenthetical abbreviations are the only place where brevity costs a bit of clarity.

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?

There is no output schema, so the description must explain returns, and it does so minimally (body plus 'complete' truncation flag). It leaves open the relationship between max_field_length and truncation and does not cover failure modes for a 3-parameter lookup tool, so it is adequate but incomplete.

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 67%; source_id and source_type are documented in the schema, and the description reinforces source_id by naming 'name/sys_id' as acceptable keys. The third parameter, max_field_length, has no schema description and is only obliquely implied by 'truncated preview,' so the description does not close the remaining gap.

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: 'Get one source record (SI/BR/widget) by name/sys_id,' which tells an agent exactly what it retrieves and how it is keyed. The abbreviations SI/BR are slightly cryptic, and no sibling tool is named for contrast, so it stops short of a 5.

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 when-to-use or when-not-to-use guidance and no alternative named, despite siblings like search_server_code, download_app_sources, and query_local_graph plausibly overlapping. The 'one record by identifier' framing implies a lookup use case, but nothing steers the agent away from a bulk or search tool.

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