Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Run a CRM view

crm_run_view
Read-onlyIdempotent

Reads records using a saved view's filters, sort, and columns. It does not change records.

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_run_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSaved view name.
limitNoPage size. Omitted means 50, and larger values are capped there.
modelYesList name on this account.
offsetNoHow many matching records to skip. Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the sentence 'It does not change records' largely restates that. The one genuinely additive point is that filters, sort and column selection come from the stored view rather than from arguments.

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?

Two short sentences, verb first, with the read-only guarantee immediately after the action. Nothing extraneous.

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?

No output schema exists, and the description never says what comes back (record list, columns per view, pagination via limit/offset). For a read tool with full annotation coverage this is adequate but leaves the return shape implicit.

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 model, name, limit and offset are fully documented in the schema. The description adds only the conceptual link that 'name' selects a stored view and that its shape drives the output columns, no extra format detail.

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 (reads records) plus the mechanism (via a saved view's filters, sort, columns). It's clear what the tool does, though it doesn't name siblings like crm_query or crm_save_view to sharpen the boundary.

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?

'Using a saved view's filters' implies the scenario (replay a stored view rather than an ad-hoc query), but there is no explicit when-to-use or when-to-prefer-crm_query guidance.

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

All Widely toolsInspect
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.

Resources