marketsharp-mcp

marketsharp_companies_get

Read-onlyIdempotent

Retrieve the connected MarketSharp company profile, including name, address, time zone, and settings, to confirm account details and configure CRM context.

Instructions

Get this connection's MarketSharp company profile (name, address, time zone and settings).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "marketsharp_companies_get"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is fully covered upstream. The description's added value is stating what the response contains (profile fields), which is meaningful in the absence of an output schema, but it says nothing about failure modes, permissions, or how 'settings' is structured.

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 the object of the call front-loaded and the returned fields compressed into one parenthetical. No filler, no redundancy.

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 zero-argument, read-only profile getter with rich annotations but no output schema, the description supplies enough to know what comes back to use the result. The only shortfall is the unexplained 'settings' payload, which an agent would have to discover at runtime.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4; schema coverage is also 100%. The description correctly adds nothing about inputs, and the field list it does give pertains to the response rather than parameters.

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 states a specific verb ("Get") and a specific resource ("this connection's MarketSharp company profile"), and enumerates the returned fields (name, address, time zone, settings). The phrase "this connection's" implicitly separates it from marketsharp_companies_list, but no sibling is named, so the differentiation is inferred rather than explicit.

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: fetch the profile of the account tied to the current connection, as opposed to listing or searching companies. There is no explicit statement of when to prefer this over marketsharp_companies_list or any prerequisite/auth context, so guidance stops at implication.

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