Skip to main content
Glama

create_survey

Generate survey, quiz, attestation, or assessment definitions in ServiceNow with configurable evaluation types, names, descriptions, and fields for structured feedback.

Instructions

Create a survey/assessment definition (asmt_metric_type). Requires WRITE_ENABLED=true

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

Input Schema

NameRequiredDescriptionDefault
nameYesSurvey name
typeNoEvaluation method: survey (default), assessment, quiz, attestation, rating
fieldsNoAdditional field values
descriptionNoSurvey description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / type / description
      Previous value: -"Metric type (e.g. \"survey\")"New value: +"Evaluation method: survey (default), assessment, quiz, attestation, rating"
  2. Addedv4.15.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the mutation profile is covered structurally. The description adds a real operational precondition (WRITE_ENABLED=true) that is not derivable from annotations or schema, which is exactly the kind of context worth crediting. It doesn't cover duplicate-name handling or what the created definition looks like, keeping it from a 5.

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

Conciseness5/5

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

One tight sentence that leads with the action and resource, then tacks on the prerequisite. No filler, no restatement of the tool name, nothing that could be cut.

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?

For a non-idempotent create with a nested free-form 'fields' object and no output schema, the definition covers purpose and the write-enabled gate but leaves open what the nested field accepts and what identifier comes back. That is adequate against a fully described schema, but not fully sufficient for a creation tool.

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 description coverage is 100%, so all four parameters (including the nested 'fields' object and the 'type' evaluation methods) are already documented in the schema. The description's mention of 'survey/assessment definition' adds no parameter-level meaning beyond that, so the baseline 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?

The description gives a specific verb plus resource ('Create a survey/assessment definition') and even names the underlying entity (asmt_metric_type), which clearly separates it from siblings like send_survey and get_survey_results. It stops short of explicitly naming those siblings as alternatives, so it sits just below the top mark.

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?

The 'Requires WRITE_ENABLED=true' clause is a genuine usage precondition that tells the agent when the call will succeed. However, there is no guidance on when to choose this over send_survey or how it relates to the bulk create variant, and no exclusions are stated.

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