Skip to main content
Glama

Подшито: инструменты юриста

О Подшито

about_podshito
Read-onlyIdempotent

Что такое Подшито и что умеет CRM для юристов, сколько стоит, как подключить личный MCP CRM к агенту, как защищены данные, контакты.

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

Input Schema

NameRequiredDescriptionDefault
topicNocrm — о CRM, price — цена, connect_mcp — подключение MCP CRM, security — защита данных, contacts — контакты

Output Schema

NameRequiredDescriptionDefault
textYes
linksYes
topicYes
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds nothing beyond that - no hint that responses are static product copy, no note that topics may be requested individually or combined - so it earns a baseline rather than a higher mark.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the topic enumeration is the useful content. It is slightly redundant with the enum descriptions but not wasteful.

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 simple read-only info tool with a fully described enum parameter and an output schema covering return values, the description supplies what an agent needs to pick the right topic. Only the lack of explicit routing guidance keeps it from a 5.

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 single enum parameter already documents every value (crm, price, connect_mcp, security, contacts) inline. The description's topic list echoes the enum rather than adding new meaning, so the baseline 3 applies.

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 identifies this as an informational lookup about the 'Подшито' product, enumerating the covered subjects (what the CRM does, price, MCP connection, data protection, contacts). The verb is implicit ('what is / how much / how to'), but the resource and scope are specific enough to distinguish it from the calculator siblings.

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 only implied: an agent can infer this is the tool for questions about the product itself, but there is no explicit instruction such as 'call this when the user asks about pricing or security' and no statement about when not to use it. Given the sibling list is entirely legal calculators, disambiguation is easy by topic, so the gap is modest.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources