Skip to main content
Glama
Sign In
mc-next-mcp-server

mc-next-mcp-server

by supanmaniar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Fetch the next page of a SOQL query

sf_soql_query_more

Fetch additional Salesforce SOQL query results by passing the nextRecordsUrl returned from a previous query.

Instructions

Fetch the next page of results using the nextRecordsUrl returned by sf_soql_query.

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

Input Schema

NameRequiredDescriptionDefault
nextRecordsUrlYesThe nextRecordsUrl from a previous query, e.g. "/services/data/v66.0/query/01g...-2000".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses the core behavior (fetching the next page) and the dependency on a prior URL, but does not mention error behavior, whether further pagination URLs are returned, or the side-effect-free nature beyond the word 'Fetch'.

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?

A single sentence with a front-loaded verb and no filler. Every word contributes to the meaning, and the structure is immediately scannable.

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 tool with no output schema, the description states the source of the required URL and the purpose. It does not detail response shape or pagination termination, but the operation is simple enough that the description is adequate.

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 100% and the parameter already has a description and example. The description adds the relational context that the URL comes from `sf_soql_query`, but does not add significant new parameter-level meaning, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Fetch') and resource ('next page of results') and explicitly ties it to `nextRecordsUrl` returned by `sf_soql_query`. This clearly distinguishes it from the initial-query sibling and leaves no ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Provides clear context: this is the follow-up pagination tool for a prior `sf_soql_query` call. It does not explicitly list when-not-to-use or alternative tools, but the dependency on `nextRecordsUrl` makes the usage boundary obvious.

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