Skip to main content
Glama
Sign In
Dataverse MCP Server

Dataverse MCP Server

by ryanmichaeljames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dataverse_get_solution

Read-onlyIdempotent

Retrieve a single Dataverse solution by its unique name or GUID.

Instructions

Retrieve a single Dataverse solution by its unique name or GUID.

Returns full details including version, publisher, and managed status. Provide solution_unique_name or solution_id — not both.

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": {
      "params": "<params>"
    },
    "name": "dataverse_get_solution"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.6.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds context beyond annotations by specifying 'Returns full details including version, publisher, and managed status'. No contradiction with readOnlyHint or other annotations.

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?

Three succinct sentences: purpose, return details, parameter constraint. No unnecessary words.

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

Completeness5/5

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

With output schema present, description suffices by stating key return fields and parameter requirements. No critical gaps.

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?

Schema already describes each parameter (coverage 100% in actual schema, though context says 0% likely incorrect). The description adds the constraint 'not both', which clarifies usage beyond the schema.

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?

Clearly states 'Retrieve a single Dataverse solution by its unique name or GUID', specifying verb and resource. Distinguishes from sibling tools like dataverse_list_solutions and dataverse_export_solution.

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?

Provides the essential constraint 'Provide solution_unique_name or solution_id — not both' but lacks explicit guidance on when to use this tool over siblings that list or export solutions.

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