Skip to main content
Glama
Sign In
rstudio-mcp-server

rstudio-mcp-server

by lerlerchan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

r_load_all

Load all functions in an R package for interactive development, allowing quick testing and iteration using devtools::load_all().

Instructions

Load all functions in an R package for interactive development using devtools::load_all()

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": {
      "package_path": "<package_path>"
    },
    "name": "r_load_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
package_pathYesPath to the R package directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. Only states it loads functions, but omits side effects (e.g., overwriting existing objects), dependencies (devtools), and potential errors (package not built). Minimum behavioral info.

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?

Single sentence of 15 words, immediately conveys the tool's action and purpose. No wasted text.

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?

For a simple tool with no output schema and one parameter, the description covers the basic purpose but lacks context on return behavior or differentiation from sibling tools. Adequate but incomplete.

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%—parameter 'package_path' is described as 'Path to the R package directory'. Description adds no extra meaning beyond the schema, hitting the baseline.

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?

Describes loading R package functions using devtools::load_all(), clearly stating the verb ('load'), resource ('all functions in an R package'), and purpose ('interactive development'). Could be more explicit about how it differs from sibling tools like r_install_package.

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?

Implies usage for interactive development, but provides no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or prerequisites like devtools being installed.

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