Conecto

Query Salesforce

salesforce_query

Read-onlyIdempotent

Run one SOQL SELECT statement in the company's org and get its records, up to 200; more says when there are others. Only reading. Free. Free.

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

Input Schema

Name	Required	Description	Default
`soql`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Adds concrete behavior beyond the annotations: a hard 200-record cap and a 'more says when there are others' pagination signal. The 'Free. Free.' fragment is redundant and unclear, and 'Only reading' merely restates readOnlyHint, but the cap and pagination note are genuinely useful additions.

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?

Front-loaded and short, but the duplicated 'Free. Free.' is wasted text and the choppy fragment style ('Only reading.') is less clear than a single well-formed sentence would be.

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

Completeness4/5

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

For a one-parameter read-only tool with annotations covering the safety profile and no output schema, the description supplies the key operational facts (SELECT-only, 200 cap, pagination indicator). Minor gaps remain around error handling and result shape, but nothing essential to calling it is missing.

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?

With a single parameter at 0% schema coverage, the description must carry the burden. It confirms the parameter must be a SELECT statement (ruling out DML), but omits the 4000-character limit, field/relationship syntax, and any hint about required clauses like FROM.

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: 'Run one SOQL SELECT statement in the company's org and get its records', which is far more precise than the name alone. It doesn't name how it differs from sibling read tools like salesforce_get, so it falls 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'one SOQL SELECT statement' and 'Only reading', so an agent can infer this is for ad-hoc queries rather than record writes. There is no explicit guidance on when to prefer this over salesforce_get or how to handle the 200-record cap.

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

All Conecto 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.

Resources

Need Help?