Sinh Vũ Studio

tim_case

Tìm dự án Sinh Vũ đã công bố (65 case ở sinhvu.com/case/) theo ngành, dịch vụ hoặc từ khoá. Trả khách hàng, một câu tóm tắt, dịch vụ đã làm, đường dẫn. Chỉ case đã công khai.

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

Input Schema

Name	Required	Description
`nganh`	No	Tuỳ chọn. Mã hoặc tên ngành.
`dich_vu`	No	Tuỳ chọn. Mã hoặc tên dịch vụ (A1, bao bì, website...).
`tu_khoa`	No	Tuỳ chọn. Từ khoá tự do (tên khách, sản phẩm).
`so_luong`	No	Số case tối đa, mặc định 6, trần 20.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 20, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses the result fields (khách hàng, tóm tắt, dịch vụ, đường dẫn), the dataset scope (65 cases), and the public-only constraint. It doesn't detail errors or sorting, but for a read-only search tool this is solid.

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 compact sentences: the first states the action and filters, the second lists outputs and scope. Every sentence earns its place with no filler.

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 search tool with no output schema, the description covers the return fields and constraints. It could mention the default/cap on so_luong, but that is already in the schema, so overall it is adequate.

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%, so the parameter descriptions already define each field. The prose only restates the filtering intent (ngành, dịch vụ, từ khoá) and adds no new meaning beyond the schema, matching the baseline of 3.

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 and resource: 'Tìm dự án Sinh Vũ đã công bố' (find Sinh Vu's published projects), and defines the search dimensions (ngành, dịch vụ, từ khoá). It is clear, but it does not explicitly differentiate from sibling tools like tim_dich_vu or tim_nganh, so it stops short of a 5.

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?

The description gives clear context for when to use the tool: searching published Sinh Vu cases by industry, service, or keyword, and only public cases. It does not mention alternatives or exclusions, but the intended use is evident.

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

All Sinh Vũ Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?