Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

get_portal_component_code

Fetch ServiceNow portal component code fields, including widget, provider, and script include bodies, in one call so you can analyze complete code without chunking.

Instructions

Fetch widget/provider/SI fields. Returns full body by default. Never chunk for analysis.

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": {
      "table": "<table>",
      "sys_id": "<sys_id>"
    },
    "name": "get_portal_component_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
fieldsNoSpecific code fields to fetch
sys_idYes
script_offsetNoRare: only when fetch_complete=False. Leave 0 for normal use.
fetch_completeNoDefault True: full body in one call. False only for >12KB single-field reads.
script_max_lengthNoRare: chunk size when fetch_complete=False. Leave default unless field >12KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.8
    • addedInput schema / properties / fields / description
      Added value: +"Specific code fields to fetch"
  2. Addedv1.22.7
  3. Removedv1.22.0
  4. First observedv1.18.41

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden. It does disclose two meaningful behaviors: the full body is returned by default, and chunking is discouraged for analysis. It says nothing about permissions, response shape, error behavior, or what happens when a field exceeds the chunk threshold.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but the telegraphic style costs clarity: '"Fetch widget/provider/SI fields"' and '"Never chunk for analysis"' are cryptic to an agent without prior context about the domain.

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

Completeness2/5

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

This is a six-parameter tool with no annotations and no output schema, yet the description is three short fragments. It omits which tables are valid, what the returned body looks like, and why chunking should be avoided, leaving substantial gaps for a retrieval tool of this complexity.

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%, with the schema already describing fields, script_offset, fetch_complete, and script_max_length. The description reinforces the default of full retrieval and discourages chunking, adding some intent beyond the schema, but it does not clarify the valid values of 'table' or the relationship between table and sys_id.

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 uses a specific verb and resource: it fetches code-bearing fields (template, script, client_script, css) for a widget/provider/'SI' record. It is reasonably clear what is retrieved, but the abbreviation 'SI' is never expanded and the tool is not distinguished from close siblings such as get_widget_bundle or search_server_code.

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?

The only guidance is an implicit directive: '"Never chunk for analysis"' and the note that the full body is returned by default. There is no statement of when to pick this tool over alternatives, no prerequisites, and no conditions under which a different sibling should be used.

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