Widely

Save a CRM view

crm_save_view

DestructiveIdempotent

Saves filters, sort, columns, and display on one list. display is table, cards, or board. A board needs group_by, a column with choices. Calendar is not available yet. The list screen reads that view. It does not add a page. A card is dragged only when no action sets that column and booking times do not use it.

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

Input Schema

Name	Required	Description
`name`	Yes	View name. Saving the same name replaces that view.
`sort`	No	Field to sort by.
`model`	Yes	List name on this account.
`columns`	No	Field names this view shows.
`default`	No	When true, the list uses this view.
`display`	No	table, cards, or board. A board needs group_by. Calendar is not available yet.
`filters`	No	Field filters, the same shape as crm_query filters.
`group_by`	No	A column with choices. The page shows this view as a board, one column for each choice.
`direction`	No	asc or desc. Defaults to asc.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedInput schema / properties / display

Added value: +{
+  "description": "table, cards, or board. A board needs group_by. Calendar is not available yet.",
+  "enum": [
+    "table",
+    "cards",
+    "board"
+  ],
+  "type": "string"
+}

Changed1 schema field changedNov 1, 2026

addedInput schema / properties / group_by

Added value: +{
+  "description": "A column with choices. The page shows this view as a board, one column for each choice.",
+  "type": "string"
+}

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare not-read-only, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds real constraints (a board requires group_by on a column with choices; calendar display is unavailable), but the closing sentences ('It does not add a page', 'A card is dragged only when no action sets that column and booking times do not use it') are too obscure to convey behavior, and overwrite semantics are left to the schema.

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?

Five short sentences, but the last two are garbled domain jargon that an agent cannot act on, and there is no front-loading of the save-vs-run distinction. Wording that cannot be interpreted is not earning its place.

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 nine-parameter, non-idempotent-looking (mutating) tool with no output schema, the definition covers the display/group_by interaction but says nothing about permissions, what the response contains, or whether saving under an existing name destroys the prior view beyond a one-line schema note. Adequate but with clear gaps.

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 the schema already documents all nine parameters, including the display enum and group_by meaning. The description largely restates schema wording (board needs group_by, calendar unavailable) and adds no syntax or shape detail the schema lacks. 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?

States a specific verb and resource: saves filters, sort, columns, and display on one list. That distinguishes it from crm_run_view and crm_query by implication, though no sibling is named explicitly. The purpose is clear without opening the schema.

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: you save a view configuration so 'the list screen reads that view.' There is no explicit when-to-use, no when-not-to-use, and no pointer to crm_run_view for reading a saved view or crm_query for ad-hoc querying, which is the natural alternative an agent would weigh.

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

All Widely tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.