Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Status

get_status

Probe the Profili installation to verify paths, database row counts, GUI status, and platform notes before running database or analysis operations.

Instructions

Probe the Profili installation: paths, database row counts, whether the GUI is running, and platform notes. Call this first.

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": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. "Probe" and the enumerated read-only subjects imply a non-mutating diagnostic, and the output schema covers the return shape, but the description never states outright that nothing is modified, nor what happens if the installation is absent or unreachable.

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?

Two sentences, front-loaded with the substantive content and closed with the actionable directive. No filler, no restatement of the title.

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?

The presence of an output schema means the return values need not be described, and the description covers the diagnostic's scope well. The gaps are the undocumented install_dir parameter and the absence of any failure-mode or read-only statement for a tool whose whole purpose is environment inspection.

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

Parameters2/5

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

The single parameter install_dir has 0% schema description coverage and is not mentioned anywhere in the description. An agent cannot tell from either source whether it overrides installation discovery, what the default null resolves to, or what format the path takes.

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?

Uses a specific verb ("Probe") against a specific resource (the Profili installation) and enumerates the scope: paths, database row counts, GUI running state, and platform notes. That enumeration also separates it from siblings like launch_profili and close_profili, which act on the GUI rather than reporting on it.

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?

"Call this first" gives explicit sequencing guidance that an agent can act on without inference. It stops short of naming a when-not condition or pointing to a specific alternative tool, but the ordering instruction is unambiguous.

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